sjc999

Why the message “PHP is NOT allowed in your code (disabled by your theme or a plugin)” when it your own plugin that is disabling it. It’s bad enough to change the default so people’s sites break – but making them think this is coming from elsewhere – not your own settings – is really bad form.

Just found and updated to 3.7.3 – the missing style problem is fixed – though it is still processing pages when set to only process posts.

Currently using 3.7.1 – that bug is present there too – but only for the top of the post.

I tried activating the exclusion settings for script/style – no difference seen. TBH I can’t think of a good use case for highlighting tags in the middle of a block of css or javascript – surely that can only break things. If the name of my tag showed up in the image name in an <img> tag I wouldn’t expect the s.w to alter that either.

I also see other changes that appear in my post that seem to be coming from Taxopress – e.g. it changes <br/> to <br> – again the change disappears if I disable the plugin.

3.7.1 reversion fixed my issues on the front page – which seems to be due to this issue – which makes me think that 3.7.2 started to interact with my front page – even though Auto Links is only enabled for posts.

I tried reinstalling the revised version of 3.7.2 and checked that. I can confirm that if I add a tag to the front page and add the matching text it is actually linking the text – even though this is a page and Auto Links is only on for posts.

This version also loses styles at the top of the post, as well as some that come from shortcodes, but others further down the page appear unaffected. The exclusion option for styles/scripts appeared to make no difference.

• This reply was modified 1 year, 7 months ago by sjc999.
• This reply was modified 1 year, 7 months ago by sjc999.
• This reply was modified 1 year, 7 months ago by sjc999.
• This reply was modified 1 year, 7 months ago by sjc999.
• This reply was modified 1 year, 7 months ago by sjc999.
• This reply was modified 1 year, 7 months ago by sjc999.

Unfortunately the new version you sent me has another problem – it seems to be stripping all inline style markup from my site – this also happens on the front page – even though Auto Links is only turned on for Posts.
To test it just add <style>.junk {display:none;}</style> to the top of your post in html mode and then view the page source and look for ‘junk’. It will be there till you active taxopress – then it disappears.

• This reply was modified 1 year, 7 months ago by sjc999.

Thanks – that seems to have fixed it.

Confirm this too – have a whole block of text repeated multiple times.

Thanks. All working now.

One more question. Does the h tag need to be a direct descendant of the class, or will it work for any descendant? Thanks

Thanks.
Presuming .xxx is the class, is there any significance to the $selectors[‘xxx’] part? IOW, if I’m not using Elegant Themes, could I just add the class “et_bloom_below_post” to my div since it is already in the the plugin, and will mean nothing to my own theme? Or am I missing something? Thanks

Unfortunately the content is dynamic.

I saw an example of processing $content
I’m thinking maybe using to regex to replace everything between two markers with a blank before passing it to the plugin. Can that be done? Thanks

Thanks

Thanks. Got that part. What I was hoping for was some code I could use inside the visibility field that would return the id of the destination page – sort of like:

get_post_meta(get_the_destination_id(),’mycf’, true )

Beginning to look like that isn’t possible. I guess I have to add them all manually. Thanks