Miguel Peixe

mouffles, turned out it works using this code:

<!-- mfunc comments_template(); --><?php comments_template(); ?><!-- /mfunc -->

Don’t ask me why, this feature really lacks an official documentation…

Also getting white page with:

<!-- mfunc comments_template(); --><!-- /mfunc -->

anyone got this working?

Nevermind, I though em_content_pre would work with single event output. It filters the events main page.

In case anyone wonders wich filter works on single event, it’s em_event_output_single.

Cheers

I simply use CSS

.breadcrumb:before {
 content: 'You are here: ';
 display: inline;
}

Hey @logikal16

I saw you implemented the formatting option, but it’s a bit buggy.

First of all, on line 93 of the wysiwyg.php you forgot to put the first parameter on $this->get_option. It should look like this:

$formatting = $this->get_option($field, 'formatting', 'default');

Second, the formatting option is being saved twice as an array, so I get this result when I successfully get the data:

$formatting = array('formatting' => 'none', 'formatting' => 'none');

Temporarily I’ll check the first value from the array, until you upgrade the fixes to a new version. Like this:

$formatting = $this->get_option($field, 'formatting', 'default');
return ('none' == $formatting[0]) ? $value[0] : apply_filters('the_content', $value[0]);

Thanks

Any news on this matter?

Awesome @logikal16! Thank you very much ??

I know what you mean but it creates lots of other problems for me. By concept the_content filter should be able to increment data. WordPress should have another filter for that, or a different filter to work with non-direct-content formatting. Agree?

I’m still going to work with wpautop for now, I’ll never use shortcodes, attachments, smiles, or anything like that in my wysiwyg…

Thanks a lot, though ??

Got the issue, but it’s still not working.
It’s not preventing the recursion here.

Can I suggest using wpautop function instead of applying the_content filters to the wysiwyg field? Or making it optional.

Seems to me that it’s a mix of a WordPres and a CFS bug. I think people do put their custom fields data using the_content filter and it should be able to work fine…

If it helps the discussion, someone also had this problem with the Advanced Custom Fields plugin
https://support.advancedcustomfields.com/discussion/2245/applying-the_content-filters-on-wysiwyg-fields-should-be-optional/p1

Thanks a lot for the support. I’m temporarily changing the wysiwyg field code directly on the plugin, til I get a better solution for it. If I put the custom fields directly on the template it’ll mess up my theme structure plans :/

Same problem

var_dump($post) outputs correctly.

It’s really strange to me that $cfs->get(); works on single.php template but not inside the_content filter, why would that happen?

Even trying to get a single field, like $cfs->get(‘author’), I get the same result…

Hi logikal16,

Actually I don’t think that’s the issue, using $cfs->get(); on the same post outside the content filter works fine and my memory limit is already set to a higher limit.

Is it possible that there’s a bug on $cfs usage inside a WordPress filter?

I already did, actually, I removed the rich snippets implementation, but I really hate doing that. Now I have to keep checking the updates and change everytime… It should have a switch-off button on the admin settings.

I built my own rich snippets system, based on my website contents.

About the div/span thing, both of them work with rich snippets, it’s the attribute that counts, doesn’t matter the element.

Cheers

It does include semantic attributes for the rating, using schema.org’s “product” and “aggregaterating”.

I still think it’s not a good idea to use “product” as a default and non-customizable semantic for my content, since I’ll use it for recipes, local business and other stuff…

Would be nice to have it customizable, at least.