Forum Replies Created
-
AuthorPosts
-
Hi Ferry,
Could you check the credentials please – they do not work for me.
Best regards,
GünterJanuary 23, 2020 at 2:43 pm in reply to: WPML + Page Content component issue (Resuable, Translatable blocks) #1177627Hi,
The local wpml_config.xml is no longer used by WPML. It is only left because some other translation plugins might use it.
Translation of page id in links should normaly happen by WPML.
So if you are in e.g. german and add in shortcode av_postcontent a link to a german page and translate the page to e.g. french WPML should translate the link in av_postcontent to the french translation of that page in the link – if it exists.
If this does not work – this is a bug in WPML in my opinion – and should be fixed by WPML compatibility team.
Best regards,
GünterHi,
Can you give us a link to your site and WP admin and FTP credentials so we can check what is going on behind – and what files are created.
The only idea I have is that due to security settings on your server the created compressed file cannot be read and is generated again and again.
We added a timestamp to the filename in one of the previous releases because we had bug reports that changes to e.g. Quick CSS were not rendered because the basic filename did not change and browsers did not recognise that they need to load the changed file.
Can you check with your hoster that files in dynamic_avia folder can be created by php user and also be read by php user – resp. by the user the scripts are running.
Best regards,
GünterJanuary 23, 2020 at 10:43 am in reply to: WPML + Page Content component issue (Resuable, Translatable blocks) #1177516Hi,
The shortcode would be something like:
[av_postcontent link='page,3848']
As much as I’m concerned WPML manages the translation on their own server in a config file.
Best regards,
GünterJanuary 22, 2020 at 12:55 pm in reply to: How to disable tabs on element edit in new enfold?? #1177165Hi,
Forgot to mention:
Goto Enfold -> Layout Builder -> Options Toggles In Modal Popup
If you are also interested: please open a new thread so we can give you the link and password.
Best regards,
GünterJanuary 22, 2020 at 11:38 am in reply to: How to disable tabs on element edit in new enfold?? #1177127Hi,
See private content. You will need an external program like winrar to unzip the file and upload with ftp to your server.
If you need assistance please provide WP and ftp credentials and we can help you.Best regards,
GünterJanuary 22, 2020 at 10:01 am in reply to: How to disable tabs on element edit in new enfold?? #1177083Hi,
We added already theme options to next release (4.7.3 or maybe 4.7.2.1) that allow to use the “old design” without toggles feature.
If you want we can provide you a beta version. Let us know.
Best regards,
GünterHi,
User must accept cookies – then the cart works.
We will add an option where essential cookies will work even if user does not accept cookies. If this is legal – it is up to you to decide.
Please have a look here for more info: https://kriesi.at/support/topic/enfold-4-7-1-cookie-consent-problem-with-woocommerce-cart-still-exists-%f0%9f%98%b1/#post-1176332
Best regards,
GünterJanuary 21, 2020 at 7:42 pm in reply to: issue: button not linking to _blank target since 4.7.1 #1176914January 21, 2020 at 4:42 pm in reply to: issue: button not linking to _blank target since 4.7.1 #1176824Hi,
Interesting – in buttons we have
<a>
links.
I think I found a better solution – replace 642 with:
var a = document.createElement('a'); a.href = url; a.target = '_blank'; a.rel = 'noopener noreferrer'; a.click(); return false;
Best regards,
GünterJanuary 21, 2020 at 12:49 pm in reply to: issue: button not linking to _blank target since 4.7.1 #1176688Hi,
This is caused by ‘noopener noreferrer’ see enfold\js\shortcodes.js 642:
window.open( url, '_blank', 'noopener noreferrer' );
Seems to be for security reasons that FF opens a new window and not a new tab. If you remove ‘noopener noreferrer’ it opens in a new tab.
Best regards,
GünterJanuary 21, 2020 at 11:46 am in reply to: Main container wrap bugged if color section or grid row is first element on page #1176659Hi,
Glad we could help you.
Enjoy the theme and feel free to come back if you need further assistance.
Best regards,
GünterJanuary 21, 2020 at 10:48 am in reply to: Main container wrap bugged if color section or grid row is first element on page #1176647Hi,
Right before return try to add the following:
wp_reset_postdata();
With $my_query->have_posts() you alter the main query and this seems to break the everything.
I would recommend not to use the WP loop for secondary queries but create your own loop using foreach and $my_query->posts.
Best regards,
GünterHi,
For your information:
We will add an option for the next release where you can disable the accordions in the ALB modal popups.
Best regards,
GünterHey amrod1,
Thank you for using Enfold.
At the moment not. But we will add an option for the next release where you can disable the accordions.
Best regards,
GünterJanuary 21, 2020 at 10:22 am in reply to: ENFOLD 4.7.1: Cookie (Consent) Problem with Woocommerce Cart still exists 😱 #1176632Hi,
We will add an option “Accept essential cookies on pageload, user must opt in for other cookies”.
This will allow essential cookies by default (like WC cart, enfold cookies) and user must opt in for other services.
Should be in 4.7.3.
Best regards,
GünterJanuary 20, 2020 at 6:48 pm in reply to: Button: Open the link in a new window does not work anymore #1176386Hi,
Sorry for the problems. It will be fixed in the next update (is planned today/tomorrow).
Please check https://kriesi.at/support/topic/issue-button-not-linking-to-_blank-target-since-4-7-1/#post-1176236 for a closer explanation.
Best regards,
GünterJanuary 20, 2020 at 6:08 pm in reply to: ENFOLD 4.7.1: Cookie (Consent) Problem with Woocommerce Cart still exists 😱 #1176375Hi,
It is clearly explained in the docu:
Option User must accept and must opt in, only essential cookies selected
If a user does not address the settings and only accepts cookies the site will have all basic functions excluding external services – this is an intuitive behaviour and what a user would expect.
As everything is blocked until user clicks the accept button this is GDPR compliant (there are discussions, but many people interpret the rules that a user cannot refuse essential website cookies).To allow website owners to be on the safe side using add_theme_support(‘avia_privacy_basic_cookies_unchecked’); will also uncheck the 2 toggles.
And also:
Only the 2 toggles “permanent hiding message bar” and “enable essential cookies” selected, all other unchecked, services blocked until user accepts settings.
There is no need to accept other cookies like GA for WC cart to work.
Best regards,
Günter-
This reply was modified 5 years, 5 months ago by
Günter.
Hi,
Thanks for reporting – could reproduce it. Seems you have deactivated in contact form but still active in theme options.
As a quick fix you an deactivate reCaptcha in theme options. In the next update there will be a fix if active in theme options and deactivated on contact form.
Release should be within the next day(s).
Best regards,
GünterJanuary 20, 2020 at 3:29 pm in reply to: ENFOLD 4.7.1: Cookie (Consent) Problem with Woocommerce Cart still exists 😱 #1176332Hi,
Please check https://kriesi.at/documentation/enfold/privacy-cookies/#default-cookie-and-services-option-settings for a closer description to “Default Cookie Behaviour”.
As it says: User must opt in for Cookies to work.
There are browser and js security restrictions to access and remove cookies – you only get info about the cookie name, but not the path. Enfold tries to remove cookies only in path “/” by default. As my dev surrunding is on a localhost the site is called with localhost/xxxx – and WC adds their cookies to path xxx. Therefore the cart worked for me, on your site WC uses path “/” and therefore cart cookies are removed – as expected until accepted.
As long as user does not explicitly accept cookies – or if user disallows cookies later – Enfold removes them if possible. We decided to use this strict implementation to be on the safe side for all users.
What you are talking about would be an option: Accept essential cookies on pageload, user must opt in for other cookies.
I will add this feature request to our repo and will check with Kriesi for an oncoming release.
Best regards,
GünterJanuary 20, 2020 at 11:39 am in reply to: issue: button not linking to _blank target since 4.7.1 #1176236Hi,
Sorry for this.
Rewriting the link selection for the toggles and moving the code to a template for easier maintenance I missed, that for some elements linktarget was used as id and for others link_target.
Already existing pages still work as expected, only new created elements or after saving an existing element the linktarget _blank might be broken.
This will be fixed in the oncoming release 4.7.1.1 (planned for this afternoon).
In case you created new elements or saved existing ones there is a fallback included to ensure that these elements will work.
Best regards,
GünterHi!
Thanks for reporting this.
Translations are normaly provided by users – but I updated the de_DE file.
And I added the CSS for the iframe.Will be in next update 4.7.1.1 – should be rekeased today afternoon,
This is a mistake in the translation file (all 3 options are translated to same string – so they overwrite each other and only “Elements” is remaining.
I fixed it in the fr_FR fie.Will be in next update 4.7.1.1 – should be rekeased today afternoon,
Best regards,
GünterJanuary 18, 2020 at 1:32 pm in reply to: Fatal error: Too few arguments to function handler_avia_widget_text() #1175814Hi,
Hm, means that php cannot find/read/open the updated file.
How did you update the file content? With WP theme editor?
If you give us ftp access and WP admin credentials we can update it for you.
Best regards,
GünterJanuary 18, 2020 at 11:27 am in reply to: Fatal error: Too few arguments to function handler_avia_widget_text() #1175790Hey Barnez1,
Thanks for using Enfold and for reporting this.
The plugin seems to call the WP filter widget_text with too few parameters. I added default values to our parameter list – this should fix the problem.
Will be part of the next update.
Meanwhile you can replace enfold/framework/php/function-set-avia-frontend.php with:
Best regards,
GünterHi,
Could you provide wp login credentials to your backend testumgebung please in private content so we can check the settings.
At a first glance I thought it could be WPML but I’m unable to reproduce it in my dev surrounding.
Since 5.3.1 WP changed the way it splits the data attributes for target “_blank” links to add “noopener noreferrer” . “_” is not supported by WP (imo a bug) and WP removes these attributes (there is no filter to avoid this). So we had to add a workaround (function avia_targeted_link_rel). As the 2 other icons have no target=_blank they are displayed correctly.
Best regards,
GünterHi,
I’ve been in backend – deactivated all plugins – and also switched to 2020 standard WP theme. The problem consists also for 2020 and no plugins active. – so nothing Enfold specific.
You need to rerun SSL-Migration.
I will ask the team if they have any idea – maybe you can check with your hoster if he knows something.
Best regards,
GünterHi,
As said before – we are not able to reproduce the problem with our user id’s. We like to help but we must be able to reproduce the problem.
Best regards,
GünterHi,
It works with all settings Enfold offers.
Can you please provide us the user id so we can check from our server?
We do not have an problems with our test is’s we have. So it is hard to locate and fix the problem.
As far as I know Instagram has limitations for access. It could be that if you are using a shared hoster this IP address could be blocked because of too much traffic.
Best regards,
GünterHi,
Can you please provide us the user id so we can check from our server?
We do not have an problems with our test is’s we have. So it is hard to locate and fix the problem.
As far as I know Instagram has limitations for access. It could be that if you are using a shared hoster this IP address could be blocked because of too much traffic.
Best regards,
GünterJanuary 15, 2020 at 4:46 pm in reply to: ENFOLD 4.7.1: Cookie (Consent) Problem with Woocommerce Cart still exists 😱 #1174591Hi,
I tried to reproduce the problem on my dev server – not able. It works fine for me also when refusing cookies.
I see js errors from a button plugin.
Also I see, that paypal is adding and deleting cookies.
Try to disable all plugins except Enfold and WooCommerce – clear server and browser cache and check. Then enable one plugin after the other and check.
And also have the developer console open and check for js errors.
Best regards,
Günter -
This reply was modified 5 years, 5 months ago by
-
AuthorPosts