Krzysztof Dryja (Aspexi)

Similar issue here.

The problem is the class-styles.php file. It’s included in gf_stla_show_css_frontend function which seems to be loaded in frontend only but it’s loaded in admin as well.

My workaround is to change the code from:

	function gf_stla_show_css_frontend($form){

		//show css in frontend
		$style_current_form = get_option( 'gf_stla_form_id_'.$form['id'] )

To:

	function gf_stla_show_css_frontend($form){

		if( is_admin() )
			return $form;

		//show css in frontend
		$style_current_form = get_option( 'gf_stla_form_id_'.$form['id'] )

Suggestion / fix from plugin’s authors much appreciated @wpmonks.

• This reply was modified 7 years, 1 month ago by Krzysztof Dryja (Aspexi).

Thank you!

Fair enough. Thanks.

Solving due to inactivity.

This explains a lot! Thank you dwinden.

Thanks Mike.

Some kind of workaround for me was enabling W3 Total Cache -> Object Cache. No deadlocks so far.

Same issue here.

Is there anything we can do with the WooCommerce code to debug / fix this?

I’ve just had similar issue and the fix was to relax files permissions, wp-config.php set to 664 instead of 644.

Be careful as it’s not always secure and you may need to change your server settings instead.

Same issue here. delete-expired-transients did not solve the problem.

Any ideas or workarounds?

I’ve just had the same issue – any change to the iThemes Security config (latest Pro) does not change .htaccess. Moreover somehow my .htaccess did not have any iThemes Security code (and the plugin have been there for years including .htaccess change). I assume it must be the result of recent issue with resetting options after upgrade. Can you guys confirm this?

I fixed this by disabling “Allow iThemes Security to write to wp-config.php and .htaccess.”, saving settings and enabling that option again.

Weird!

Hi Stefano,

Did you solve this issue?

Krzysztof

I repeated this twice.

The only thing is that the site is running on cpanel hosting with suExec, so there might be some issues with files permissions, however plugin works after activation from the plugins list so no idea what’s the problem.

This might be WordPress bug as well.

Thanks @tripflex for your comment.

Due to several reasons plugin is no longer in active development.

I have plugin rebuilding from scratch in my 2014 schedule (including hiding wp-login.php) though.

Please contact me directly if you have any suggestions about current version of the plugin (dryja at aspexi dot com). Thanks and sorry for that issue.

@jagesso new version has been released. iPad / iPhone issue has been fixed. Simply click again on facebook button to close window.

This is my solution for this problem https://dryja.info/events-manager-and-wck-custom-fields-and-custom-post-types-creator-conflict/