well thanks for the replies
not sure where all this got me
hopefully some newbies may benefit
(particularly about two shortcodes side by side)
I may find your plugin useful …?
Advice: your links to other shortcode tutorials are onfusing since they suggest block encoding and saving definitions in the theme functions.php and not in the database.
FWIW I don’t think it was an anti spam issue which caused the saving issue, since somehow it was saved sometimes
Question: Why (and is there a difference) are there two identical settings for your plugin
1. under “settings”
2. under “Tools”
could that have caused the saving issues(I don’t see how) but maybe you can give it some thought.
once again thanks
P.S.
apologies to anyone who may not like the caps, but FWIW I personally think clarity makes them valuable
I will admit that all caps is offensive
OK I think I understand the problem with saving, and why it went wrong
– although I may not explain it well.
As a newbie I was attracted to the “live test” shortcode ability of the plugin
Also as a newbie, I need to experiment.
So I created a test shortcode based on the “age” example from the support site.
Here is the seed of the problem.
The age example requires a parameter so I happily test and save what I think works – because indeed in the test page it does.
However, by the time the shortcode name(s) are saved in the database the shortcode with parameter [age birthdate=”Mar 20, 2010″] becomes “age birthdate=”
I have looked at the database entries and indeed there is an “age” and an “age birthdate=”
Of course I tried to delete them from the plugin test page – but no luck.
Perhaps understandably the presence of the 2 similarly named shortcodes may explain why they did not work?
Also, since the plugin source code is encrypted, I have no idea what may be the problem – but it could be an easy fix….?
Hopefully this is somewhat enlightening.
Plugin Contributor
M66B
(@m66b)
I think I see your problem. Shortcode definitions should not include brackets and parameters (these should be decoded in PHP code, see the WordPress documentation for how to). Brackets and parameters should only be included on shortcode usage, for example in a post. Updating and deleting a shortcode definitions with brackets and/or quotes may be impossible, because of database escaping done by WordPress.
The source code is open source, a requirement to be listed on wordpress.org, and not encrypted in any way.
OK no parameters and quotes – I am getting it figured out
and thanks again for the response
regarding encryption In my Plugins/Edit page:
Editing shortcode-exec-php/shortcode-exec-php-class.php (inactive)
Select plugin to edit:
<?php if (!WPShortcodeExecPHP::Get_option(c_scep_option_donated)) { ?>
<form action=”https://www.paypal.com/cgi-bin/webscr” method=”post”>
<input type=”hidden” name=”cmd” value=”_s-xclick”>
<input type=”hidden” name=”encrypted” value=”—–BEGIN PKCS7—–MIIHXwYJKoZIhvcNAQcEoIIHUDCCB0wCAQExggEwMIIBLAIBADCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2
is the highlighted area not encrypted?
I am fairly sure it is your plugin – no?
Plugin Contributor
M66B
(@m66b)
That is the standard PayPal donate link. The source code of the plugin itself is open source as said before.
