Forum Replies Created
-
AuthorPosts
-
The hot fix for the icon box issue can be found here: https://kriesi.at/support/topic/click-to-add-your-own-text-here-error/#post-1311590
Apparently, a new Enfold update to address these issues is due for release early next week.
One approach is to hold off on the theme update for a week or two until any minor bugs have been reported and fixed, or, better still, create a staging site on a subdomain and use that to test updates before pushing to the live site.
Good luck!
I can access the site too: https://snipboard.io/9Ni6qz.jpg
Try clearing your browser cache.According to this post by the Autoptimize author, you need to add
wp-includes/js/dist
and possiblywp-includes/js
to the excluded js list.Then, suggested in this post, you can exclude the following:
/jquery-?[0-9.]*(.min|.slim|.slim.min)?\.js /wp-includes/js/dist/vendor/wp-polyfill.min.js /wp-includes/js/dist/vendor/lodash.min.js /wp-includes/js/dist/api-fetch.min.js /wp-includes/js/dist/url.min.js
- This reply was modified 3 years, 8 months ago by Barnez1. Reason: addition info added
I am aware of the issues when users update to CF7 5.4. After testing, I today updated from v.5.3.2. to v.5.4 and all 3 forms are sending without any problems. The site is running the latest Enfold version and has Layerslider enabled. The site does not use a caching plugin (Enfold performance enabled: js and css compression) and does not use reCaptcha. Looking at the threads on the CF7 support forum, having reCaptcha enabled and use of third-party caching plugins seem to be relevant to the issues arising.
Currently, you don’t even need to install the Classic Editor plugin, just select the option from the theme options:
Given the popularity of the Classic Editor, I believe that in terms of support until or as long as is necessary, the later will apply.The exact verbage is:
Classic Editor is an official WordPress plugin, and will be fully supported and maintained until at least 2022, or as long as is necessary.
With 5 million active installs and installs increasing (link), my opinion is that Classic Ediror will still be maintained by WordPress for several more years at least. If there is a decision to abandon the project, then I woudl expect an independent developer to take over the Classic Editor project.
Classic Press is another option, but you are right in that compatibility with Enfold is not assured, nor with other plugins you may use.Excellent. Regarding your other query, that probably requires a custom plugin to be developed.
You can add the following code to the functions.php file of the child theme to show the raw html in a field at the bottom of the edit page/post, below the ALB builder. Then, add your shortcodes(?) to wrap the required html:
/*set builder mode to debug so html code is visible*/ add_action('avia_builder_mode', "builder_set_debug"); function builder_set_debug() { return "debug"; }
Or, I guess you could try disabling the ALB builder to show the raw HTML and add your shortcodes(?) that way.
Ah. In that case, how about: https://wordpress.org/plugins/content-control/
Content Control allows you to do the following:
– Display certain content on a page/post to logged in users only
– Display certain content on a page/post to specific user roles
– Display certain content on a page/post to logged out usersI use the Members plugin that allows you to set permissions to protect/show post/page content based on the user role.
Enfold is not offically compatible with WordPress 5.6. If you check in the forum, there are several issues being reported, probably due to the jQuery changes in WP5.6, and possibly resolved by installing the Enable jQuery Migrate Helper plugin. Many folks are holding off the update to 5.6 until Enfold has been updated and is officially compatible. Even then it would be worth trialling on a staging site first if your client sites are complex.
Proceed with care on production sites:
WordPress Core aims to be compatible with PHP 8.0 in the 5.6 release (currently scheduled for December 8, 2020).
However, PHP 8.0 is a major version update with a large number of changes that break backwards compatibility, and many features that were deprecated within the PHP 7.x feature releases have been officially removed.
Significant effort has been put towards making WordPress 5.6 compatible with PHP 8 on its own, but it is very likely that there are still undiscovered issues remaining.
The state of PHP 8 support within the broader ecosystem (plugins, themes, etc.) is impossible to know. For that reason, WordPress 5.6 should be considered “beta compatible” with PHP 8.
This is the email I received:
@kmac Looks fine to me too from Spain: https://snipboard.io/vMAICL.jpg
Günter,
I have the same concerns A couple of points that may help.
1) You can use the ‘compare files’ function of editors such as Notepad++ to compare the files you have in the child theme with the latest versions in the main /enfold/ theme folder. Besides, your modifications, this will show up new additions to the file in the latest version, and give you a chance to update the child theme with the latest file version, with your modifications of course then added. Make sure you keep a backup of the original child theme files just in case.
2) You can add code to the header.php file from the functions.php file using theadd_code_to_header
function. This means the header.php file can be removed from the child theme directory, and is one less file version to keep an eye on for changes after theme updates. Read more here: https://kriesi.at/support/topic/add-code-to-header/Good luck!
January 19, 2020 at 6:05 pm in reply to: Fatal error: Too few arguments to function handler_avia_widget_text() #1176026Hi,
Yes. Please mark the topic as resolved and close it. Thanks again for the quick fix.
Best regards,
BarnezJanuary 18, 2020 at 3:05 pm in reply to: Fatal error: Too few arguments to function handler_avia_widget_text() #1175827Hi,
Yes, you’re right. I created the php file again using Notepad++, uploaded and all is well. I can confirm the fix works.
Many thanks for your attention to this.
Best regards.January 18, 2020 at 1:04 pm in reply to: Fatal error: Too few arguments to function handler_avia_widget_text() #1175812Hi Günter,
Many thanks for looking into this. When I replace the
function-set-avia-frontend.php
file with the modified version, it throws a different error as follows:[18-Jan-2020 10:58:56 UTC] PHP Warning: require(/home/xxxx/xxxx/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php): failed to open stream: No such file or directory in /home/xxxx/xxxx/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 167
[18-Jan-2020 10:58:56 UTC] PHP Fatal error: require(): Failed opening required ‘/home/xxxx/xxxx/wp-content/themes/enfold/framework/php/function-set-avia-frontend.php’ (include_path=’.:/opt/cpanel/ea-php73/root/usr/share/pear’) in /home/xxxx/xxxx/wp-content/themes/enfold/framework/php/inc-autoconfig.php on line 167Regards,
BarnezJanuary 16, 2020 at 6:01 pm in reply to: URGENT: How do I rollback to a previous version of Enfold? #1175147Happy to hear that helped. Yes, hooray for backups! I need one myself today :)
January 16, 2020 at 5:10 pm in reply to: URGENT: How do I rollback to a previous version of Enfold? #1175126Or you can try just updating the /themes/enfold directory to see if that is enough to fix your issue without meddling with the database
January 16, 2020 at 5:07 pm in reply to: URGENT: How do I rollback to a previous version of Enfold? #1175122Do you have a pre-update backup of the site files and database? If so, you could restore the database and replace the existing /themes/enfold directory with the one from the backup. All this is carried out through your control panel provided by your host (e.g. in cPanel you would use the File Manager to restore the theme directory and phpMYADMIN to restore the database). Note that this will restore the site to the state when you made that backup. So if the backup is from 22 December 2019, all settings/text/images etc changes since will be lost.
May 4, 2019 at 12:44 pm in reply to: Remove the update nag for LayerSlider plugin bundled with Enfold [Fixed] #1097172Hey Rikard,
Yes, this is fixed.
Best regards,
DamianApril 5, 2017 at 10:30 am in reply to: Bundled Layerslider: Any news on update due to secuirty issue #772370Hi Rikard,
Please feel free to close this topic.
Thanks!April 4, 2017 at 11:15 am in reply to: Bundled Layerslider: Any news on update due to secuirty issue #771656Hi Victoria,
Since the release of v.4.0.5 all my concerns have been resolved! It’s reassuring to see Enfold responding swiftly to a vulnerability in one of its bundled plugins. As a user of the theme this gives me additional confidence in your team and priorities.
Thanks for getting back with the notification.Hey Yigit,
Thanks for getting back. Yes, all resolved now. There was an issue with a plugin that was cauding the problem, now fixed.
Best wishes,
BarnezFebruary 1, 2016 at 5:04 pm in reply to: Layerslider problems: slider stops loading and can only be resolved by resaving #575898Hi Rikard,
I’ve already tried clearing the cache and disabling all the plugins with no success. To summarise this thread, the following did not resolve the issue:
1. Clearing the browser cache (Firefox)
2. Using a different browser (Chrome)
3. Clearing the caching plugin (SuperCache)
4. Disabling *all* plugins at the same time
5. Deleting and re-uploading the Enfold theme files
6. Turning off image preload in the LayerSlider settings
7. Deleting the images from the Media library and re-uploading fresh versions of the imagesWhat finally seems to have worked is using relative urls for the images in LayerSlider. I made this change 3 days ago and so far, things seem to be resolved. I will leave this thread open for another week just in case the problem returns, but the early signs are good.
Regards,
BarnezJanuary 28, 2016 at 10:07 am in reply to: Layerslider problems: slider stops loading and can only be resolved by resaving #573584Hi Rikard,
I spoke to soon :( The issue is back. It looks like every time a setting is changed and saved in LayerSlider the slider is refreshed and the images load. But after <24 hours the images stop loading again, with the “It seems like the URL of the image or background image …..” error message. So, I’m back to asking if you have any further suggestions. All plugins are up to date as well as WordPress, and this is a recent issue as the slider has been working fine for 5 months. I’ve tried adding relative urls for the images, but as I have just saved the settings I will need to wait <24 hours to see if this has helped. I will include login details below if you want to take a took in the Dashboard and see if there are any issues.
Thanks,
Barnez- This reply was modified 8 years, 9 months ago by Barnez1. Reason: More info + login details
January 27, 2016 at 1:51 pm in reply to: Layerslider problems: slider stops loading and can only be resolved by resaving #572858[Resolved]
In Dashboard >> LayerSlider WP >> Misc I turned off image preload and the slide immediately returned.
January 27, 2016 at 12:10 pm in reply to: Layerslider problems: slider stops loading and can only be resolved by resaving #572779Help!
I’ve deleted and then re-uploaded the images, left the slider for 24 hours and the problem is back again:
It seems like the URL of the image or background image “xxx.jpg” is pointing to a wrong location and it cannot be loaded. Please check the URLs of all your images used in the slider.
What should I do?
January 26, 2016 at 9:54 pm in reply to: How to extend theme support after purchase on Envato #572391Just to update, I have the following reply from Envato support:
The option to extend support will be available in a week or two.
-
AuthorPosts