Posted 8 months ago #
I've just installed this and it does work well fixing posts and pages but what about custom post types? It hasn't fixed any of them and I have quite a few catablog pages and of course all the spacing has gone from them as well. Is there any way to fix them too?
http://wordpress.org/extend/plugins/preserved-html-editor-markup/
Posted 8 months ago #
@denl - It should work for custom post types as well. They should be listed under the Admin > Settings > Writing : "Configure New Line Behavior Per Post Type" section.
Are you saying that you've tried using the "Fix XXXX" buttons on your custom catablog post types and they don't wrap the content in paragraph tags? Be sure to follow the directions however as that those content fixes are not reversable without restoring to a database backup.
It is possible that a custom post type also loads some custom code that causes a conflict with my plugin. Can you verify that this is the plugin you are referring to? http://wordpress.org/extend/plugins/catablog/
If so I'll review the code and see what's going on. It sounds like they alter the WYSIWYG editor after reviewing their readme file.
Posted 8 months ago #
Actually I'm not sure its working at all. Just checked the page I was trying to make after using the plugin and I still haven't got paragraph tags. I have many many nested code display none tags! No p's at all. I count 14 nested code tags around 1 comment. Blimey. But no paras at all. Perhaps I missunderstood what the plugin does?
This is what some of my html looks like...
'<code style="display: none;"><code style="display: none;"><code style="display: none;"><code style="display: none;"><code style="display: none;"><code style="display: none;"><code style="display: none;"><!-- product -->'
I tried fix posts and fix pages under new line behaviour, those worked on posts and pages but not on the catablog pages and yes, it's that plugin. I did a backup first so I can restore if I need too..
Posted 8 months ago #
I do have it set to both br and p in the settings and I am using firefox, so maybe that's why I have no paragraphs? Also I tried to put in paragraphs using the visual editior and double enter.
I've tried just copying and pasting my html across into html mode and that works perfectly! Phew! No strange nested code tags.
So now I just need to work out how to update the pages using catablog.
Posted 8 months ago #
Yeah, the code style display none pieces are my way of hiding comments from the WYSIWYG editor. I don't store that in the database, it get's stripped out on save. It's the only way to preserve mutli-line html comments, and it was easiest to just do all comments that way. But it sounds like catablog uses them in the visual editor and so we're probably stepping on each other's toes.
If you find a solution before I do please let me know. I'll download the plugin either tonight or tomorrow and take a look at what's going on. I'll be sure to follow up as soon as I can.
Thanks,
Marcus.
Posted 8 months ago #
Ah! No that was me not explaining myself very well. I wasn't working on a catablog page, I was working on a normal wp page in draft mode and looking at it in preview mode, and I had comments in there for my own reference, so I guess that's why I got all those nested code tags. Plus I'd been trying to get the html in the page to work properly for hours until I came looking for a solution and found your amazing plugin. So I was proably crosseyed as well. :-) But I deleted the page, tried it again, and it worked perfectly. And thank you!!!!! It's a god send!
The catablog item pages are not updating when I use Fix post or fix page, so I have some missing p's and br's in them. All the actual wp pages and posts have updated, its just this custom post type that hasn't. But just in case I'm missing something obvious, you say theu should be listed under Writing : "Configure New Line Behavior Per Post Type" but I only see fix pages and fix posts there, no custom post types. Should there be a Fix custom post types as well?
thanks for your help, its much appreciated
Den
Posted 8 months ago #
Well that is excellent news to hear you have it working well with posts and pages. You should actually see a button for every post type. So you should see "Fix Catablog" and additional "Fix XXX" buttons for each custom post type. I set it up that way in case certain custom post types were previously not intended to be used with wpautop - as is the case with my Content Molecules plugin.
But there are two settings that can prevent that button from displaying - if the plugin disables the "show_ui" setting or does any custom/non-standard adjustment to the "post_type_supports('editor')" function. I've got some time to look into the catablog plugin this morning so I'll see what I can find.
And of course you do have the option of manually updating them, but I'd wager you have a lot of pages :/ Another option is I could write a php script that directly updates the database tables catablog uses to store its content. I could release this as a separate plugin or just publish it for manual download. But I'll see if I can fix the problem directly first.
Thanks,
Marcus
Posted 8 months ago #
Well that was simple, probably should have just read the code first instead of replying to you. They configure their custom post types without the default admin GUI - ie show_ui is set to false. I can remove this check in my plugin because it was a false assumption on my part that unless they had a UI they wouldn't have an editor attached to them. But in the case of catablog they create their own UI and inject the tinymce editor manually. Simple fix, should be updated before lunch.
Posted 8 months ago #
Ok, just published an update, should be available in the next 15 minutes or so.
Posted 8 months ago #
Thanks Marcus!!!!! That worked a treat. :-)
What a fabulous plugin this is! Thank you so much. Yes i do have a large number of catablog pages but I'd have happily worked through them all for the convenience of using preserved mark up. It so worth it!
Thanks again!
Den
Posted 8 months ago #
Awesome, glad to hear it. (this post is mostly to keep my name as the last person to post, so I can keep up with which problems are resolved :D)
You must log in to post.
