The function to copy snippets to another site.
Accept QueryString value
Allow the insertion of querystring values (GET in PHP) into values of a snippet. For example: [wbcr_php_snippet id=”xx” title=”Safely process a GET Form Submission” submitted_value=”–value of $variable in querystring–“]
Insert automatically on specific pages
Insert shortcodes automatically on specific pages.
use name instead of id in the shortcode
for example [wbcr_php_snippet id=”xx” title=”Safely process a GET Form Submission” submitted_value=”–value of $variable in querystring–“] will be more clear and maintainable if will became [wbcr_php_snippet name=”my_unique_name” title=”Safely process a GET Form Submission” submitted_value=”–value of $variable in querystring–“]
in this case every update or delete/creation of that snippet obviously generate a new id but with this upgrade we won’t be to change id=”old_value” with id=”new_value” inside all site!!!!
Eliminate unused css and js
Nice feature would be automatic elimination of unused css and js code. I know that this is a pretty complex matter, and no plugin has solved this problem.
But if you manage to successfully achieve this, you can freely raise your prices – I’ll be first to spend my money on plugin with this functionality!
Export all tags, also scripts files with their modified names
custom shortcode names
Use Case Scenario:
Developer uses shortcodes and snippets in all client sites. Developer uses the same shortcodes for template type content.
– Site Title
– Site URL
– Site Admin Email
– anything really…
Issues with current shortcodes:
– The “Woody” shortcodes would be different on each site. The developer would have to make sure that each shortcode matches all of the shortcodes on each template page.
– The shortcodes would change everytime they are imported, created or re-created on a site.
– Woody shortcode names don’t provide any useful info to developers or front end users. If there is an error with the plugin, the php, or if the plugin is accidentally disabled… then the users on the front-end see a shortcode that doesn’t make any sense. A more functional driven development are shortcode names which provide some clear information as to what the shortcode is trying so display. For example, instead of shortcode named like this: [wbcr_snippet id=”37″], it could be named like this [site-name]. Providing a name for the shortcode gives clear insight that the shortcode is probably there to provide the website’s name. So even if there the shortcode isn’t working, it still provides info to the user. It also provides the developer clear info.
Execute PHP within custom excerpts
Some themes work such that if one wants to show additional content on a page using a given template, such as a bit of text and links, then one has to put it into the page’s custom excerpt. If one additionally were to have such areas be dynamic, such as using a bit of code to randomize what’s shown within, then Woody Snippets’ shortcodes would need to be able to optionally execute not just before or after excerpts, but also within them.