headelf

Thanks Mike. That’s perfect. I have to individual checkboxes now which is what I wanted.

You might want to include this in the documentation somewhere . . . or if it’s already in the documentation, add it again in the instruction for the advanced options.

Thanks muchly.

Nori

There’s a checkbox in the settings for TinyMCE advanced for this, but checking the box to “Stop removing the <p> and <br /> tags when saving and show them in the HTML editor” is going to give you a completely different, and equally unappealing problem.

With the option checked, TinyMCE Advanced will now automatically add coding for paragraph/line breaks and it will do it every time the page is refreshed in the visual editor. If you save the page in the visual editor, when it reloads, you will find new code added that separates the existing paragraphs with an additional. And to make matters even MORE interesting, every time you save it and it reloads the page, it adds more coding. When you try to navigate away from the page it tells you the page has changed and are you sure you want to navigate away without saving. At this point I’m going to do a REALLY girly thing and roll my eyes at this lovely little feature.

The less than ideal but workable solution for this is to uncheck the option, add the html coding in the html markup window and save the page WITHOUT VIEWING IT in the visual window. It’s the act of viewing it in the visual window that mucks with your coding.

As to the unauthorized cleanup of your code, if you got to the forum for TinyMCE you will see there’s a way to shut down the “cleanup” function which is what strips out your custom code. Until that option is added to the MCEadv plugin you’ll have to re-add the code each time the plugin is updated.

I solved this. It’s a hotlinking images issue.

To prevent image hotlinking some scripting needs to be added to the .htaccess file for the wordpress site.

You can find the generator at https://www.htaccesstools.com/hotlink-protection/

Here’s the tip. Paste the result onto the last line of the existing .htaccess file.

It gets even worse . . . for those of us using justified images. I both left and right justify images. I have no beef with left justify, it seems to work fine, adding hspace (l/r margin) around the image and centering the caption, but the left align SUCKS. Not only does it NOT center the caption, it also doesn’t add hspace.

Where is the consistency here? I had to fiddle and I HATE having to fiddle when the programming should handle this consistently.

ElfN

You need to change the records in the database to reflect the new domain. I just went through this same process and have everything working except . . . there’s always an “except”.

I can log into admin, but once I have I get a blank screen.