Recent Topics

1 Jan 29, 2015 12:07    

I've done an upgrade from 2.4.5 to 5.2.1-stable (well i know, quite a long time between the versions...). The upgrade-process itself went fine but after that, i've two issues i cannot solve:

1. the old (and also newly created) postings don't have linebreaks (CR/LF) anymore, they're lost or are not created if a linebreak is just inserted with hitting the Enter-key. In the Edit-View of the backoffice, they're there but not in the preview and the published view. At the moment i manually add <br /> tags to get linebreaks in the postings for formatting my postings readable. This behaviour differs from the previous version.

Second problem, there's no TinyMCE-Editor in the Backoffice. The Plugin is enabled (in general and in the user-settings) but it won't be shown in the editor. I've disabled and reenabled it, enabled and disabled the compressor - no change.

Any hints are welcome and help is appreciated.

2 Feb 14, 2015 11:20

Hi @c3d,

Having lost the linebreaks (that actually are <p> tags) of your old posts sounds pretty weird. Do you see HTML code when you open them up in the editor? In any case, please make sure that the Auto P plugin is enabled in your site and checked in your posts. That way, b2evolution will automatically surround each paragraph between <p> and </p> tags.

Also, is the Allow HTML parameter checked for your current blog? (http://b2evolution.net/man/blog-features-settings) When it is unchecked, the WYSIWYG editor is not available.

Regards!

3 Feb 16, 2015 19:57

Hi @mgsolipa,

thank you for your response. I'm not really sure, what you mean with seeing HTML code when opening the postings in the editor - i see some HTML tags, but not one for <p>. For clarification, i've added some screenshots.

The Allow HTML parameter is checked (see also attached screenshot - i've merged several screenshots together, hope it's not too confusing).

I'm a bit lost.

4 Feb 20, 2015 07:16

Well, something isn't working as it should. Even without WYSIWYG editor, there are several buttons missing from the toolbar at the top of the content field.

Just to confirm, please make sure that the "Auto P" option is checked in the "Text renderers" section at the expert editor (see screenshot above). Also, the Apply rendering to posts parameter for that plugin should be set to "opt-out" at Structure > Your blog > Plugins. More information about Apply rendering can be found here: http://b2evolution.net/man/plugin-apply-rendering

Please, try creating a new blog and make a post. That blog will be created with default settings, so it should behave correctly. Finally, you can also enable debug mode and check if there is useful information in both, back-office (post editor view) and front-office (post view).

We will be waiting for your feedback.

5 Feb 20, 2015 19:12

Ok, i guess things are getting a bit clearer, somewhere something went wrong.
I've created a new blog, same thing here as in my old blogs.
The Apply rendering to posts parameter for the "Auto P" Plugin is set to "opt-out" - but (as you can see in the pic above), in the expert view of the editor the Text Renderer field is empty.
It says "no renderer plugins are installed".
That's strange, because the plugins are marked as installed in the global Plugins-List (as shown in the screenshot in my previous post).

I've activated debugging, but for me it looks all quite ok. No error messages here.

Any hints what to check further?

6 Feb 21, 2015 11:21

All right @c3d,

You need to enable debugging for plugins, which is disabled by default. In order to do that, please go to the file inc/plugins/model/_plugin.class.php and replace the line

$GLOBALS['debug_plugins'] = false;

with

$GLOBALS['debug_plugins'] = true;


Note: remember to switch it back to false after the problem is solved.

Regarding the issue itself, it's like the installed plugins are not detected in the edition form. Please, go to the post edition form (expert mode) and look for the plugins output section (it should look like the image above). Try to find messages like "get_by_ID(): Plugin (ID ... ) not registered/enabled in DB" or "Requested plugin [# ... ] not found!". Even "No registered plugins" or "Registered plugin IDs" could be there in the debug output. Most of those messages are not necessarily marked as errors.

7 Feb 23, 2015 12:26

I've set the debug_plugins to true. The created output looks good to me. As far as i understand this, the plugins path and the plugin itself is correctly found and loaded - or am i wrong?


Form is loading...