Nextendweb

Hi @aszele,

The applications written in PHP should not cause memory leaks as PHP server should free up all the memory on every page load. Memory leaks are caused by the PHP core, which is really hard to fix at the application level. If you check the changelog of PHP 8, you will see that there are a ton of fixes for different memory leak problems. This is why I think the best bet to update the PHP runtime for the latest version.

Here is one, which I think might be related: https://github.com/php/php-src/issues/8646 It’s memory leak in PHP 8.1 FPM which was fixed in PHP 8.2.5.

Thanks, I have just sent it to you!

Hi @willcycle,
I just checked the installer what my colleagues sent you in the first reply and compared its content with the one we released today. I can confirm that everything was in the right place in that installer and the fix was the right one. There is no change between the two installer which relates to this problem. We never told you that we missed any file from the installer, what my colleagues meant that some file might not get overridden on your server by the installer. But it’s just one of the possible explanation for this situation.

I’m not sure what happened, but as a result some files stuck in their old version on your website. As the install process is handled by WordPress and your server, we are unable to tell what was exactly the cause. When this happens, we always suggest to try with FTP file upload as a workaround. It might happen that the old PHP files were stuck in the PHP OPcache. It’s very rare and very hard to tell…

@timbearcub,
Smart Slider 3 will be fixed soon. We will use the following filter without using shortcode in the future:

/**
* Filters the content of a single block.
*
* The dynamic portion of the hook name, $name, refers to
* the block name, e.g. "core/paragraph".
*
* @since 5.7.0
* @since 5.9.0 The $instance parameter was added.
*
* @param string   $block_content The block content.
* @param array    $block         The full block, including name and attributes.
* @param WP_Block $instance      The block instance.
*/
$block_content = apply_filters( "render_block_{$this->name}", $block_content, $this->parsed_block, $this );

Hi @chris-yau,
We had an unexpected issue with one of our servers. We fixed the problem and now all of our services should work as expected. Thank you for reporting!

Thank you @meteor1ecwid!

Hi @inthischest,
thank you for your feedback. This is the first time that we had to remove a “feature” from Smart Slider 3, but the intention of this feature removal is not to sell more pro package. We had to make this change to comply with www.remarpro.com repository rules which does not allow to include unfiltered HTML input from user input. So we must filter every input field and we can only allow HTML codes which meant to be allowed for the given context. As you probably used Text layer in the past to include custom HTML into your sliders, your iframe gets filtered out with this update. Text layer is a paragraph and it meant to be contain only text specific HTML codes, like bold, italic and links.

HTML layer was always been a pro feature and that layer would be the perfect for your use case as it allows to place iframe tag.

Hi @imtester,
Smart Slider 3 itself does not send out any kind of emails. Also we do not know any kind of vulnerability which would make Smart Slider 3 to send out spam emails.

I suggest you make a full security audit on your site. Check core WordPress files, plugins and themes source code for clues. It might happen that a malware created new PHP files or infected existing files which might give you assumption that a specific plugin is the root of the spam emails.

Could you share us the details what you found?

Thank you @epsiloncool!

@daanvandenbergh, I tried it, but the free version of OMGF was not able to catch the Google font injected by Smart Slider.

As not every page/post contain sliders, we inject stylesheets and scripts with an output buffer as needed. Your free version only parse through the enqueued styles for Google fonts, so it is not able to catch ours.

If you give me a private pro access, I can give it a try to see if it works or not.

Also I’m open to find solution to support your free version with a custom hook. Our limits are that we can not wp enqueue the Google fonts and we can only tell the Google fonts url after the wp_footer done. Probably you use output buffer in your pro version, but for this case you should use that too in the free version.

Hi @daanvandenbergh,
we are dropping that Google Font implementation in version 3.5. Probably it will be released on the next week.

I red through your plugin description and I think Smart Slider itself will be compatible only with the pro version of your plugin as we do not simply enqueue the Google fonts. Does your plugin have a public api in the free version where could hook the Google fonts for free users too?

Please contact with me at [email protected] to discuss the details. Thank you!

Hi @deeveearr,
thank you for reporting this issue. We had an error on our end. We were able to fix this, so you should be able to send us your email. Could you try it again?

Hi @a223123131,
the beta version of Smart Slider 3.5 is out: https://smartslider3.com/blog/smart-slider-35/

The stable release will come on the next week if there are no serious bugs in the beta.

Hi @barnabas1,
I’m the developer of Smart Slider 3. We got your support request and we were able to solve this issue in Smart Slider 3. One of my colleague will send you the fix soon. Thank you for reporting this problem!

@a223123131 I think you had CPU throttling enabled or simulated throttling disabled while you ran Lighthouse 7.0.1 that’s why you might get lower scores.

These metrics are lab data and not the real world data. Google will use the real world (called field data) data as far as I know. https://imgur.com/a/gyPijz2

Test version (JavaScript files are not minified), Lighthouse 7.0.1 with simulated throttling off, device: mobile, sliders from the homepage of smartslider3.com: https://i.imgur.com/kXNIerG.png