Forum Replies Created
-
Posts
-
The update allowed the slide to be shown but constricted to body of site, not the expected full screen.
Just upgraded Revolution slider to 6.05. Still getting error:
Notice: Undefined index: height in /home/xxxx/public_html/wp-cci-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_revolution.php on line 112Does not work when using full screen. Could not wait for a fix so I rebuilt the slider using LayerSliderWP.
All three of these sites hung on maintenance screen and then 500 error after deleting maintenance file.
Being this was a repeat from the last updated. Been there done that we knew how to recover.
Sorry but did not inspect all the directories since time was of essence to get sites back up.
Delete Enfold directory and loaded copy of updated version.Site #1
GoDaddy Shared
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
PHP 7.1
max_execution_time 30
memory_limit 128M
post_max_size 8M
upload_max_filesize 2MSite #2
Bluehost Shared
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
Php 7.0
max_execution_time = 30
memory_limit = 256M
post_max_size 64M
upload_max_filesize 64MSite #3
GoDaddy Shared
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
PHP 7.1
max_execution_time 30
memory_limit 128M
post_max_size 8M
upload_max_filesize 2MGood site without any issues
Site #4
Atlantic VPS
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
PHP 7.1
max_execution_time 60
memory_limit 256M
post_max_size 256M
upload_max_filesize 25MWordPress states “When developing Themes, it’s good to keep in mind that your Theme should be set up so that it can work well with any WordPress plugins users might decide to install.” https://codex.wordpress.org/Theme_Development
Imagine if you are the author of an SEO plugin and would have to make special arrangements for everyone who decides to break this WP standard. I would ask myself why should I spend my time and resource$ to fix a problem setup by someone else?
Kriesi developers made a choice to include functionality that is not compatible with a plugin that looks for SEO source content in the normal WP location. Kriesi should work with SEO Yoast to bring the Enfold theme and probably a lot of others back to WordPress core tenant of themes working well with plugins.
The large question here is: Has Kriesi talked to Yoast development? It is quite possible Yoast might help them add functionality to the Kriesi themes.
I think this should be checked out: http://kb.yoast.com/article/151-i-cant-save-seo-data-when-using-avia-layout-builder
I tried this without success.
It is agreed it would be unreasonable to support every plugin. Plugins with a major following like Yoast SEO which provide an essential service to the WordPress community need to be supported. Especially if Yoast folks stepped up and provided instructions to allow a seamless integration with their code by any theme using a proprietary editor. A check box in the theme options would work best to turn on the compatibility.
Kriesi has sold us a great theme with a good but proprietary editor that enables great control over the payout of posts and pages. Avia Layout Builder is a selling point. It works well as advertised.
Yoast SEO provides a great tool to help users setup the SEO for each page/post in a educational way. It is one of the most widely used SEO plugins. It should not be required to write custom code for every optional editor.
The solution lies with Kriesi. There should be option in any theme using the Avia Layout Builder to use the code suggested by Yoast to make the content generated by the Avia Layout Builder visible to Yoast SEO.
I am not sure where to turn here. There are three parties involved in this issue. Should this issue be fixed by the plugin, theme and or page builder author? The SEO plugin was designed for use for the WordPress platform and the native built in editor and a standard location of the content. If a theme chooses to use a different editor that stores the content elsewhere the theme developers and advance page builders should use common code to allow any plugin to “see” all content regardless of it’s location. Sort of like an alias path.
If I has the background to develop a WP plugin that works with the WP core I don’t think I should be required to add code at my own expense to support a third party plugin.
I think this is on the page builder folks to work together for a common solution within the WP framework. Isn’t the Avia Layout Builder is an Kriesi product?
