Darko A7

I have manually removed entire tmpWpfc dir, not sure why it was used / created in the first place.

This seems to be a leftover from an older plugin version, before it was moved. Closing this for now…

• This reply was modified 4 years, 2 months ago by Darko A7.

Oh, I think I have found a serious bug.

tmp folder is full of endless folder “loop” with amp pages:

e.g. tmpWpfc > 12345678 >
page-url > amp > https: > domain.com >
page-url > amp > https: > domain.com >
page-url > amp > https: > domain.com >
page-url > amp > https: > domain.com >
page-url > amp > https: > domain.com >
page-url > amp > https: > domain.com > index.html

I have counted 6 itterations in total!

• This reply was modified 4 years, 2 months ago by Darko A7.

Hi,

I have discovered a serious issue with pre_get-posts method. It affects Admin Dashboard as well! It hides this post from being visible in the table of all published posts!

Of course, it can be resolved by checking if backend is being accessed, but “raw” version you have on your website is not good.

Regards

Ok, got it. Thanks!

It works great, perfect for my use case. Still, I wonder why you opted out for this “crude” solution that affects all alm queries? I mean, don’t get me wrong, we can tweak function further ourselves, adding additional conditions, but why no support for shortcode or custom param?

Just curious, nothing else ??

Thanks,
Regards

Thank you for your fast response! I googled the solution before posting, but obviously didn’t find this. Many thanks!

Please, disable all other plugins and revert temporarily to stock WordPress theme, clear your browser’s cache, reload affected page(s) (or use CTRL + F5, works in Chrome), and see if the issue disappears.

If the answer is yes, start re-enabling one-by-one all other plugins, and repeat above procedure, to catch the culprit. Then, please report the issue to the respectful developer.

I cannot reproduce this on my end. Marking it as ‘resolved’ / not an issue.

Since you haven’t responded, I assume you figured the issue on your end, most likely caused by another plugin or theme.

Thanks, can you post a screenshot or tell which headings are affected / on which page?

No problem, I do however recommend either converting that “mod” into a plugin or use it in a sub-theme, otherwise every main theme update will lose those custom changes.

Hi, no, not without some additional code and modifications. It was not the intention of this plugin to change the Editor’s font.

Check this here to get some idea (not tried, can’t confirm it will still work in latest WordPress):

https://stackoverflow.com/questions/47619233/how-to-change-the-default-font-of-tinymce-for-wordpress

Regards

Same here, happened during upgrade to version 5.4.0 .

Just hit back to admin url, database upgrade was separately requested (never happened before, though), hit it and seems all good so far.

Hi, plugin is supposed to behave like that, it is by design. Plugin is created with simplicity in mind, I’m afraid support for custom exclusion css rules is going to be beyond what ordinary users know how to do, but maybe I can add input text box for that in the future.

Except for eye at admin login page, I haven’t noticed anything else missing.
Some screenshots, guides, clues would be nice.

Hi, I have seen some changes in latest version:

// if(current_user_can( 'manage_options') || !get_option('comment_moderation')){
if($comment_approved === 1){

I am not sure from security perspective that avoiding user privileges check is a wise thing to do. It was better before imho. Yes, approved comment status can only be done by users who can approve them, but once approved, comment can be edited as well, and maybe through some other plugin or function put in the new approval (waiting) queue. Just my thought… could be wrong.