michael_greenberg
Forum Replies Created
-
Forum: Plugins
In reply to: [PHPEnkoder] Causing a error 400 with payment gatewayI am done maintaining this plugin, but my bet would be that our javascript conflicts with theirs. You can use the
[noenkode]to disable the enkoder on certain pages. Good luck!Forum: Plugins
In reply to: [PHPEnkoder] Conflict with Lazy Loader >= 4.1, make priorities customizableIt is! If you’re interested in having these changes made, please file a PR at the github page (https://github.com/mgree/phpenkoder/).
Forum: Plugins
In reply to: [PHPEnkoder] Compatibility with PHP 7.1 and 7.2Can you post a log with
error_reporting(E_ALL)? It’s working fine on my install at 7.2…- This reply was modified 7 years, 10 months ago by michael_greenberg.
Forum: Plugins
In reply to: [PHPEnkoder] WooCommerce Checkout conflictUnfortunately not—sorry to be unhelpful! 🙁 It might be worth raising the issue with the WooCommerce folks, since they’ll atleast be able to point you to the part of the code that’s generating that page.
Forum: Plugins
In reply to: [PHPEnkoder] WooCommerce Checkout conflictOkay, I’ve taken a look, so feel free to change it back. It’s hard to see what the conflict is, since checkout.js has been minified and isn’t exactly the smallest bit of code.
I think the simplest thing to do is to disable PHP Enkoder on that checkout page. (I doubt it will have material impact on what spam you get, since it’s pretty far in.) If WooCommerce has an explicit page, all you need to do is write the
[noenkode]shortcode at the top of the page. If it’s a PHP file (probably inwp-content/woocommerce-checkout/index.php), you can manually edit the PHP to turn off PHPEnkoder by calling ‘enkoder_unregister_filters()’ after requiring/importing the appropriate WordPress headers. Please let me know if that works!Forum: Plugins
In reply to: [PHPEnkoder] WooCommerce Checkout conflictHmm… can you temporarily put up a version of the site with PHPEnkoder running? It’s hard to tell where it would go wrong, though there seem to be a couple of @ signs that might confuse it…
Forum: Plugins
In reply to: [PHPEnkoder] Doesn’t work…Oh, one other thing that may work, without editing any PHP: you can try using the [enkode]TEXT[/enkode] shortcode in your header or footer to manually encode something.
Forum: Plugins
In reply to: [PHPEnkoder] Doesn’t work…By default, PHPEnkoder only works on the main content of the page, not the header or footer. You can register other filters, if you like, by tweaking the source code. Add whatever filters you like to line 214. Alternatively, you can have the footer manually call the ‘enkode’ function via PHP. If you’re not sure how to do this, please send me an email.
Having options to control where PHPEnkoder runs would be nice, and I’ll add it to my [TODO list](https://github.com/mgree/phpenkoder/issues)… but I’m not certain what kind of timeline I’ll be able to work on.
Forum: Plugins
In reply to: [PHPEnkoder] conflict with visual composer 4.12I have no idea how Visual Composer works, and your problem sounds a lot like it’s *their* bug. The best thing to do may be to turn off PHPEnkoder while composing pages; hopefully the output of their tool will cooperate with PHPEnkoder’s filters.
There are two ways to turn off PHPEnkoder: you can turn deactivate the plugin through the dashboard, or you can do it programmatically by editing their or my code. You can do so by using a command like
add_action(XXX, 'enkoder_unregister_filters');, though I have no idea whatXXXshould be to work for you.I’m sorry I can’t give a better answer, but WordPress plugins are an untamed wilderness—compatibility is essentially impossible. 🙁
- This reply was modified 9 years, 7 months ago by michael_greenberg. Reason: trying to fix markup
Forum: Plugins
In reply to: [PHPEnkoder] conflict with search & filter pro, disable on pageWhen I realized how easy it would be implement, I just went ahead and did it. Version 1.14 just pushed to the WordPress Plugin Directory.
All you need to do is put
[noenkode]at the top of a page and it the plugin will disable itself for that page.Forum: Plugins
In reply to: [PHPEnkoder] conflict with search & filter pro, disable on pageYou could edit
enkoder.phpto add a hook that (a) detects the page of interest and then (b) callsenkoder_unregister_filters.You’re not the first person to want to turn off PHPEnkoder for just one or two pages—when I have time, I can implement a shortcode that will let you disable PHPEnkoder without having to edit PHP. Doubtful this will happen before September, though.
Forum: Plugins
In reply to: [PHPEnkoder] Question about format of enkode short codeThe text you write in the “text” attribute will be shown, but not the contents. So:
[enkode text="for private eyes only"]super duper secret[/enkode]Will map to
<script>... a bunch of self-evaluating JS that shows "super duper secret"</script>on browsers with JS; on browsers without JS, they’ll just get:
<span>for private eyes only</span>I might be wrong about the presence of the
span, but it’s more or less that.Forum: Plugins
In reply to: [PHPEnkoder] Comment rest showing on form pageThanks for letting me know! The HTML parser I use is ad hoc, but I’ll try to fix this case when I get a chance.
Forum: Plugins
In reply to: [PHPEnkoder] Not working on pages.My email address for PHPEnkoder stuff is up on the webpage, at http://www.weaselhat.com/phpenkoder/.
Forum: Plugins
In reply to: [PHPEnkoder] Not working on pages.Can you send me a link (by email, if necessary)? PHPEnkoder is meant to work on pages, and if it’s not it’s a bug/bad interaction with other code.