azurecurve

This is part of the azurecurve ClassicPress Plugins which introduces the plugins I have available for ClassicPress.

The plugin I am going to cover in this post, is a brand new one written for ClassicPress; To Twitter.

Functionality

Allows posts to be automatically tweeted when they are published.

Mark the Post tweet on publish/update? checkbox to post tweet when the post is published (works for both immediately and scheduled posts.

Set hashtags in the hashtags box; these appear after the tweet.

Save a draft of the post to see auto-generated default tweet and amend if necessary; to regenerate default tweet, clear Tweet field and save draft; post URL is represented by a %s placeholder.

Integrates with my URL Shortener for URL in tweet.

This plugin is multisite compatible with each site having it’s own settings.

Download

The plugin can be downloaded via my Development site.

Click to show/hide the azurecurve ClassicPress Plugins Series Index

azurecurve ClassicPress Plugins
Add Twitter Cards
Avatars
BBCode
Breadcrumbs
Call-out Boxes
Code
Comment Validator
Conditional Links
Display After Post Content
Filtered Categories
Flags
Floating Featured Image
Icons
Images
Insult Generator
Loop Injection
Mobile Detection
Multisite Favicon
Page Index
Post Archive
RSS Feed
RSS Suffix
Series Index
Shortcodes in Comments
Shortcodes in Widgets
Sidebar Login
Tag Cloud
Taxonomy Index
Theme Switcher
Timelines
Toggle Show/Hide
URL Shortener
Add Open Graph Tags
Markdown
To Twitter
Nearby
Gallery From Folder
Taxonomy Order
Snippets
Widget Announcements
Events
From Twitter
Update Admin Menu
Maintenance Mode
SMTP
Check Plugin Status
Estimated Read Time
Username Protection
Remove Revisions
Disable FLoC
Redirect
Contact Forms
Strong Password Generator
Load Admin CSS
Support for Plugins
Translating Plugins
All plugins now auto-update

I’ve done a lot of work with the Microsoft Dynamics GP Workflow module over the years since it was first released and it still seems to be growing in popularity with clients. Depending on the workflow type being created, the GL account string can be used in conditions to determine the routing for the approver.

However, commonly clients want to check the value for a single segment rather than the full account string. You can, to an extend, accomplish this using filters such as contains or begins with, but sometimes this isn’t feasible. You can get round this problem be using the _ wildcard in your condition.

For example, if I was setting up a purchase requisition workflow and wanted to configure a routing for all advertising expense codes, which is the codes where the Account segment start 66, to the Marketing Director, I could set up a condition where the account string is ___-66_0-00:

Workflow Condition error with wildcards in the account string

Workflow Condition example with wildcards in the account string

This would use this workflow step for all Divisions (segment 1) for department 00, where the Account (segment 2) starts with 66 and ends with 0. The wildcard character allows an account string with any value in the characters replaced with an underscore to be selected.