authentictech

Hello.

The site is behind this link. https://bit.ly/38w5GsO (sorry for the shortener – I prefer to keep the site private and disable the link when we’re done.)

There are two forms – one on the home page at the bottom and one on the contact page linked in the top menu.

Thanks

@shamser_suzon I can confirm that the problem I described in my opening post has reverted and is happening again in the latest plugin release.

That linked thread is one of the more helpful interactions with support I have seen on www.remarpro.com despite what appears to me to be a misunderstanding. I am not sure why that made you dock three stars from your review which seems unfair. It does not seem to be a fair representation of the plugin itself or the support experience. I wish all support on www.remarpro.com would be that helpful/responsive to be honest.

Thanks for you response.

I was informed by the web host that the problem was caused by ModSecurity – the Content-Length rule was triggered. It was resolved by the host extending the limit.

This might also affect others so hopefully it will be useful info to pass on.

(I just wish I could edit the title as it has nothing to do with the excellent Smart Slider 3 plugin ?? )

Yes, that has fixed things. Thanks very much. ??

This might not actually be anything to do with Smart Slider 3 as, after I have installed other plugins, I have noticed that the problem may be related to the fact that if the exported file is larger than 128M it will always fail to import. Previously, removing the Smart Slider 3 plugin files reduced the exported file size to less than 128M.

Although I have the PHP options post_max_size, upload_max_filesize, memory_limit and max_execution_time much higher than is necessary, the common factor seems to be exported files larger than 128M fail hang at 100% or just under.

I will discuss this with my host and update the thread.

Julie, I haven’t solved it yet, no.

Correction: This plugin in no longer works on any of my websites (although the menu link is showing on those websites).

Is the plugin abandoned?

Thanks for all your help, Kathryn. The code you provided works fine for me.

Do you foresee a fix for this in the next release of Edin or are we going to have to keep re-editing the code each time the Edin files are updated unless we can upgrade PHP?

Unfortunately, I don’t have access to a more recent PHP7 release on this shared hosting platform yet (assuming only versions prior to PHP7.1 are affected).

Can you tell me the technical cause of the problem (so I can perhaps bug my host to upgrade to PHP7.1)?

Many thanks.

PHP Version 7.0.21

I’m still getting the error running PHP 7

I’ve been using the Edin theme for several months on PHP 5.6 without any problems.

Just prior to upgrading Edin, I upgraded to WordPress to 4.8.1 and the update process timed out while incomplete so I had to upload a fresh WordPress.

I had also prior updated a few other plugins but no problems after doing that. I didn’t add any new plugins or activate/deactivate any prior to experiencing this problem.

Jetpack was installed and active but I haven’t configured or used it. I’ve now deleted it.

I’m confused. As a syntax error would mean a problem with the code itself, not a runtime error caused by other code, I don’t know what else to do and I’ve no idea why it is calling out this line of code as a syntax error.

The full, original function as taken from the code on my site is:

function edin_get_attachment_image_src( $post_id, $post_thumbnail_id, $size ) {
	if ( function_exists( 'jetpack_featured_images_fallback_get_image_src' ) ) {
		return jetpack_featured_images_fallback_get_image_src( $post_id, $post_thumbnail_id, $size );
	} else {
		return wp_get_attachment_image_src( $post_thumbnail_id, $size )[0];
	}
}

When I remove the [0] it works and when I re-add it, I get the syntax error.

I’m now using PHP 7.

As long as I leave the [0] out it works, but I’d prefer to find out what the problem is.

Any idea where I should go next?

Thanks.

It’s running PHP 5.6. Thanks.

Just confirming that the 6.1.0 release fixed my problems. Many thanks.

Thank you! ??