Vladimir Vassilev

Hey, check out author’s comment here: https://www.ads-software.com/support/topic/fatal-error-x/

You shouldn’t use the rating system for reporting issues that you have with a plugin, especially when the issue might be related to your environment and not meeting the technical requirements of the plugin.

I’ve downloaded the child theme from github that seems to be by the same author, and it seems to be working fine. I’ll stick to that, as I couldn’t invest more time in investigation of the issue I had with manually or automatically created child themes.

@lopo , excuse me, I didn’t mean to offend you by this! I wasn’t expecting a security issue to be fixed by accident after being left for so long in the wild. Obviously it was not reported responsibly this time, as Plugins Team usually make sure to contact plugin authors immediately when such cases arise.

Yeah, I just tried it and it’s fixed, the reported vulnerability is no longer reproducible. Not cool that the author didn’t announce it properly in the change log.

• This reply was modified 4 years, 11 months ago by Vladimir Vassilev.

Thank you for taking the time to reply, @phpexpert21 . I wish you tried following these instructions yourself or at least asked whether I am sure all is working well with the child theme generators.

The child theme created for Modul-R does not work correctly, no matter if the child is generated from a plugin or is created by the steps, suggested in the outdated article in WPBeginner.

Please, if you are related to the development or support of Modul-R, check what’s wrong with the theme, as it looks great otherwise and child theme supporting is a rather expected behavior.

That was quick, thanks ??

Thank you, @snehalb890 , but we already did a fix in our child theme. I’m reporting it here, as it’s clearly a thing to be updated in the styles of the original theme.

Hallo, Rohe,

You must have misunderstood the aim of the plugin, as it is not purging/clearing the cache but rather triggering the Swift Performance plugin to actually create a cached version for that specific page. The only thing this add-on does is to create a button with a link of the same page, appending ?force-cache to the end of the URL.

If you had all your cache regenerated because of a single click, you must have pressed the wrong button, or Swift Performance have changed their logic in an unexpected manner, which I doubt.

Anyway, I’m sorry that you felt mislead by the description of the plugin, but please – next time ask in the support forums before assuming a plugin is broken or useless.

All the best,

Vladimir

Here’s a correction – this issue is not related to Next Page add-on, as it behaves the same way for the default demo of Ajax Load More on their site, when visited from Snapchat.

Awesome, Darren, thanks for the quick reaction!

Sharing these parameters like “this works for me” would mean “try it out if you have problems” to anyone who does not know what the parameters mean. I find it important to mention, that these high values might bring problems to the server/hosting account, that’s all.

@logologics these are unacceptable high parameters for input vars and max post size. If you really need these in order to work with Elementor, either the plugin is written in the most terrible possible way or you are doing something completely wrong.

@khuutam I also experience problems with the latest version. The slider I’ve setup is meant to display 3 of the latest posts, but I’m getting more than 10, and are definitely not the latest :/

A client of mine has the same problem. Not sure if it was like this before they updated their site, but now they are close to server CPU consumption limit because of excess or heavy AJAX calls. It would be nice to see some response from the plugin authors on this.

• This reply was modified 6 years, 6 months ago by Vladimir Vassilev.

Yep, 0.9.9.16 fixes it. Thanks, Steve!

Thanks, @wysija! The problem with this setup is that if I set 5 separate emails for each day of the working week, each day that had less than the limit of posts posted, will send items from the previous day that have already been send. It would be much better if days could be selected with a set of checkboxes or if there was a filter for the days when a newsletter is sent, so that I could prevent sending on weekends. Does your message mean there is no other way around it?