Hi,

Thank you for using Enfold -and sorry for the late reply.

I had forwarded this to Kriesi and Yigit is currently working on rebuilding a new feature request page. But we have no deploy date yet.

Thank you for your patience and enjoy the theme.

Best regards,
Günter

Hey Jan,

Thank you very much for pointing us to this topic.

I added it to our dev features repo and keep an eye on it.

Best regards,
Günter

Hi,

FYI:

In the next update 4.7.3.1 there will be a theme option to prevent generating the timestamps.

Best regards,
Günter

Hi,

@Jason

Glad it is working for you now.

I will close this thread.

Feel free to come back when you need further assistance and enjoy the theme. Have a great day.

Best regards,
Günter

Hi,

I added a possible fix for the next update.

Depending on your performance settings it might be necessary to toggle compression of css files (and it might be necessary to save the page(s) that made problems to update enfold internal data).

Best regards,
Günter

Hi,

Glad we could help you – and thanks for the fedback.

Enjoy the theme and have a nice day.
Feel free to come back when you need further assistance.

Best regards,
Günter

Hi,

Did you clear browser cache (and also try incognito window).

If still exists, please open a new thread and provide WP admin credentials and a link to the page so we can check.

I rechecked it on my server and it works for me.

Sorry – missed, that you mean button action. Will check.

Best regards,
Günter

• This reply was modified 5 years, 1 month ago by Ismael.

Hi,

@pete4u

Behaviour of the “Accept” button depends on the options you selected in “Default Cookie Behaviour” (must opt in / can opt out).

must opt in – user has to allow explicit which services he wants to use.

Best regards,
Günter

Hi,

Did you update to 4.7.3 and clear server cache?

Best regards,
Günter

Hi,

I checked your page content on my server with include: – page loads as expected.

if you use includes: or includ: on your server your page also loads fine, also using include : does not work.

Could to be a plugin (Security ??). Can you try to deactivate all plugins and then reactivate one by one and check?

Best regards,
Günter

Hi,

Thanks for your feedback.

Enjoy the theme and have a nice day.

I will close this topic – feel free to come back when you need further assistance.

Best regards,
Günter

Hi,

A few releases ago we added a unique timestamp to the merged filename because when updating the content of a CSS or js file or of Custom CSS option without changing theme version the generated hash for the filename remained unchanged and browsers did not recognize to reload the file but used the cached version instead until this cache expires – means the changes are not visible to visitors.

The problem you have is server related. It seems that your server is caching WP database options and returning that cache instead of the last updated values.
As we save the generated filenames in WP database options Enfold gets the wrong info that the merged files do not exist and therefore creates new ones on every pageload.

For the next version (4.7.2.1 or later) I added a filter where you can remove the timestamp.

This means that each created file has the same filename and overwrites the already existing one until your server returns the correct DB value that the file exists and Enfold can stop creating new files.

To functions.php of your child theme add the following (https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/Performance/avf_merged_files_unique_id.php):

function my_custom_merged_files_unique_id( $uniqid, $file_type, $data, $enqueued, $file_group_name, $conditions )
{
return '';
}

add_filter( 'avf_merged_files_unique_id', 'my_custom_merged_files_unique_id', 10, 6 );

Best regards,
Günter

Hi,

Thanks for reporting this.

This is really caused by Enfold. I changed the logic for creating folders a bit and now the default security setting will be 755 (filterable with avf_folder_security) for new created folders. Security for already existing folders will not be changed any more.

Will be in next update 4.7.2.1 (should be next week).

If you want to have a quck fix:

In file enfold\framework\php\function-set-avia-backend.php around line 939 you find:

@chmod( $folder, 0777 );

Replace with:

@chmod( $folder, 0755 );

Do not forget to make a backup of the original file for a fallback.

Best regards,
Günter

Hey!

Thanks for reporting this.

Will be replaced by correct schema.org markup in next release.

Best regards,
Günter

Hi!

Sorry for that once again.

Will be available in the next release 4.7.2.1. (planned for next monday)

Regards,
Günter