Hi,

There seems to be a core problem in WPML. I’ve been in touch with them and they say there should be a fix in the next update.

Could you please get in touch with the guy (see in private content) who is in charge of compatibility at WPML and report the problem to him and give him access to your site so he can check everything.

Maybe he can check the fix ?

Thank you for your cooperation.

Best regards,
Günter

Hi,

Update: I opened a ticket at WPML (see link in private content) – can you add this to your ticket ?
Thx.

Best regards,
Günter

Hi Julian,

Thanks for the feedback.

I’m not a WPML expert – all I figured out was by trying to get it run on my dev servers.

The only idea I have is to check if it is really only the translation routine or some other problem (maybe WPML related) because we have another user with such a strange behaviour.

I created (and deleted again) a testpage to see if something changes with a new page – negativ. I do not want to mess around too much in your site.

Step 1: Can you upload a few new images and create a new page with a few elements like masonry, image, logoslider and translate this page and see if the problem still occurs (also add some textelements like textblock, special heading)

Step 2: Dectivate all plugins except WPML plugins and try to translate the images again without any other plugins active and check.

Step 3 would be to activate the “WPML Media Translation plugin” (if you have access to it – maybe WPML guys will give you access for testing purpose) and manually translate the images and check if this helps.

Sorry for the inconvenience but it is the only way to narrow down the problem.

Best regards,
Günter

Hi,

Thank you for using Enfold – and sorry for the problems.
WPML must have changed a lot in the implementation of translating images – this seems to break our logic.

Can you confirm, that these problem also started with updateing of WPML ?

I have tried to find a solution.

As a first step can you please update the following files:

config-templatebuilder\avia-shortcodes\catalogue\catalogue.php with
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/catalogue.php

config-templatebuilder\avia-shortcodes\image\image.php with
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/image.php

config-templatebuilder\avia-shortcodes\image_hotspots\image_hotspots.php with
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/image_hotspots.php

config-templatebuilder\avia-shortcodes\logoslider\logoslider.php with
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/logoslider.php

config-templatebuilder\avia-shortcodes\section.php with
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/section.php

config-templatebuilder\avia-shortcodes\timeline\timeline.php with
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/timeline.php

Do not forget to make a backup of the original files for a fallback and that you have updated to Enfold 4.4.1.

Then you need to translate all images that you use in Enfold Layout builder elements – you can run a WPML update routine (see link in private content):

Goto Dashboard -> WPML -> Settings and “Media Translation” at the bottom.
There you find “Media Translation Documentation” and a button “Start”. Leave all checkboxes checked.

If you need a more specific translation of images (or do not want to translate all images) I would recommend to use the WPML Media Translation plugin (https://wpml.org/documentation/getting-started-guide/media-translation/).

As far as I could test on my install this should fix the problem.

Best regards,
Günter

Hi,

Thank you for reporting this. It is actually a bug and Dude’s solution will break the standard WC shop page where Enfold adds extra select boxes for filter and ordering.

Please update config-woocommerce\config.php with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/config-woocommerce/config.php

Make sure you use Enfold 4.4.1 and make a copy of the original file for a fallback.

Best regards,
Günter

Hey Zaccc,

Thank you for using Enfold.

Enfold has support for Tribes Event Calender and Pro version
.

We are not able to give support for every plugin that is on the market.

If you are not familiar with CSS (and perhaps also PHP) you will need to contact a freelancer/developer to do the adjustments for you.

Best regards,
Günter

Hi,

Freut mich, dass wir Dir helfen konnten.

Viel Freude noch mit dem Theme und gerne stehen wir für weitere Fragen zur Verfügung.

LG,
Günter

Hi,

Gerne.

Viel Freude noch mit dem Theme und Du kannst jederzeit ein neues Topic aufmachen, wenn Du Hilfe benötigst.
Einen schönen Tag noch.

LG,
Günter

Hi,

I could fix the problem with the logoslider.

Please update file config-templatebuilder\avia-shortcodes\logoslider\logoslider.php

with https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/logoslider.php

Do not forget to make a backup of the original file for a fallback and that you have updated to Enfold 4.4.1.

Make sure, that you have translated all images with WPML Media Translation you are using in the logoslider (see link in private content).

Concerning language flags – this must be caused by a plugin – or a WPML problem. Our theme uses standard WPML functions to output the flags:

config-wpml\config.php line 257 function avia_wpml_language_switch().

Try to deactivate all non WPML plugins, all caching plugins and check. Then reactivate one plugin after the other.

Best regards,
Günter

Hi,

Thank you for reporting this.

It should be fixed with the next update.

Meanwhile you have to update file

enfold\config-templatebuilder\avia-shortcodes\av-helper-masonry.php

Please replace the complete file with

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_4_1/av-helper-masonry.php

Make sure to make a copy of the original file to have a fallback and that you are using Enfold 4.4.1.
Do not forget to clear browser and server cache after the update.

If you have problem we can do the update for you.

Best regards,
Günter

Hi Rob,

Sorry for the late reply but I’m on holiday this week.

Strange – I downloaded the file with ftp from your server (see private content). The code is correct in this file – as should be in 4.4.1.

This is the code in the file that starts at line 3019 (it is a comment line):

			/**
			 * Now we check that all directories belong to a cache entry
			 */
			$cache_dirs = scandir( $this->upload_folders['instagram_dir'] );
			if( ! is_array( $cache_dirs ) )
			{
				/**
				 * Something went wrong reading directory - folder does not exist, access denied, .....
				 * There is nothing we can do.
				 */
				return;
			}

I added the comment and the is_array check with 4.4.1.

What is also a bit strange is the the “Permission denied” message: – upload_folders[‘instagram_dir’] points to the a subdir of standard WP upload directory which should be accessible.

Best regards,
Günter

• This reply was modified 7 years ago by Günter.

Hi,

Sorry for the late reply but I’ve been on holiday last week.

I talked to Kriesi – our servers are running on multisite so this could be a problem with your settings and/or plugins.

Could you give us admin login credentials so we can check the backend – you can post them in the private content section.

Best regards,
Günter

Hey Kevin,

Thank you for using ou theme and reporting this.

I put it on our to do list and will try to add it in one of the next releases.

Enjoy the theme and have a nice day.

Best regards,
Günter

Hi,

Glad we could help you.

Feel free to come back when you need more assistance.

Enjoy the theme and have a nice day.

Best regards,
Günter

Hi,

Nein.

Wenn Du in functions.php des Child Themes (oder des Hauptthemes, wenn Du kein Child Theme verwendest) am Ende das folgende einfügst (z.B. über Dashboard -> Appearance > Editor):

add_filter( 'avf_output_google_webfonts_script', 'my_output_google_webfonts_script', 10, 1 );

function my_output_google_webfonts_script( $activate )
{
	return false;
}

dann ist sichergestellt, dass der Google js nie geladen wird, auch falls Du versehentlich einen Google Font auswählen solltest.

Best regards,
Günter