Forum Replies Created
-
AuthorPosts
-
August 12, 2016 at 9:37 am in reply to: 'sslverify = false' with 'wp_remote_get' == bad practice! #671770
Hi Andy,
Thank you for you reply.Unfortunately, Enfold v3.7.1 is what introduced this bad practice code. Just don’t do
'sslverify' => false
- This reply was modified 8 years, 3 months ago by jan_reilink. Reason: within doesn't work :)
May 30, 2016 at 1:39 pm in reply to: Regarding topic 'Enfold theme – problem with fopen() when updating the theme' #640337Thanks for that Yigit. Please keep me in the loop, since a lot of our customers – of the hosting company I work for – have these kind of issues. Not only with Enfold, but other themes like Avada, as well. From our side, we’re working with WordPress, on Trac, to resolve this in the core.
May 19, 2016 at 12:09 pm in reply to: Regarding topic 'Enfold theme – problem with fopen() when updating the theme' #635120Thank you for your reply Basilis.
Is there anything Kriesi can do to make sure download links and filenames are shorter than 255 characters? That would help a lot of users.
February 20, 2016 at 6:11 pm in reply to: Avia.js, jquery.js errors (Syntax error, unrecognized expression: …) #586500Thank you for your reply Josue! I completely forgot about that option. I removed WordPress’ jQuery as a test (quick hack) just to see whether that was the culprit, and apparently it is, in this specific situation…
Thanks again.February 20, 2016 at 9:45 am in reply to: Avia.js, jquery.js errors (Syntax error, unrecognized expression: …) #586423Thanks for your response Josue. No can do, I’m sorry (I’d have to set up the same environment on a different location for that, and I’m lacking the spare time to do so).
But: I replaced WordPress’ jQuery version 1.12.0 in
/wp-includes/js/jquery/
with the jQuery file delivered by Enfold theme (/wp-content/themes/enfold/js/mediaelement/
) as a test, and that seems to resolve the issue… Notice I’m running a development WordPress version.LOL thanks! There was no mention of any PHP7 fixes on Facebook (I know, I replied…)
Will give it a go as soon as possible, unfortunately I’m not able to apply the update today.For what it’s worth, running PHP 7.0.0RC6 now and Enfold version 3.4.1, it still gives me the PHP Error:
Fatal error: Uncaught Error: Function name must be a string in D:\www\saotn.org\www-secure\wp-content\themes\enfold\framework\php\class-style-generator.php:123 Stack trace: #0 D:\www\saotn.org\www-secure\wp-includes\plugin.php(525): avia_style_generator->create_styles('') #1 D:\www\saotn.org\www-secure\wp-includes\general-template.php(2434): do_action('wp_head') #2 D:\www\saotn.org\www-secure\wp-content\themes\enfold\header.php(51): wp_head() #3 D:\www\saotn.org\www-secure\wp-includes\template.php(562): require_once('D:\\www\\saotn.or...') #4 D:\www\saotn.org\www-secure\wp-includes\template.php(521): load_template('D:\\www\\saotn.or...', true) #5 D:\www\saotn.org\www-secure\wp-includes\general-template.php(45): locate_template(Array, true) #6 D:\www\saotn.org\www-secure\wp-content\themes\enfold\index.php(9): get_header() #7 D:\www\saotn.org\www-secure\wp-includes\template-loader.php(89): include('D:\\www\\saotn.or...') #8 D:\www\saotn.org\www-secure\wp-blog-header.php(16): require_once('D:\\www\\saotn.or...') #9 D:\www\sa in D:\www\saotn.org\www-secure\wp-content\themes\enfold\framework\php\class-style-generator.php on line 123
I believe to have fixed this by changing
$this->output .= $this->$rule['key']($rule)."\n";
to$this->output .= $this->$rule['key'][$rule]."\n";
( changed () to [] on line 123 of enfold\framework\php\class-style-generator.php ). Not sure this is the right fix, but PHP no longer reports errors when I have error_reporting enabled.
- This reply was modified 9 years ago by jan_reilink.
No problem Rikard, I’ll try to fix errors myself as they show up. However, it’s time to start working on compatibility; PHP 7 is coming soon (October, November 2015). I expect a lot of users want to jump on it as soon as it arrives, because of the performance improvements.
Thanks for your prompt reply Basilis!
Strangely enough, Enfold didn’t notice me of an available update. Anyway, I updated to 3.2 and the PHP Fatal error persists:
[02-Jul-2015 11:04:33 UTC] PHP Fatal error: Uncaught Error: Function name must be a string in D:\www\saotn.org\www\wp-content\themes\enfold\framework\php\class-style-generator.php:123 Stack trace: #0 D:\www\saotn.org\www\wp-includes\plugin.php(503): avia_style_generator->create_styles('') #1 D:\www\saotn.org\www\wp-includes\general-template.php(2271): do_action('wp_head') #2 D:\www\saotn.org\www\wp-content\themes\enfold\header.php(49): wp_head() #3 D:\www\saotn.org\www\wp-includes\template.php(537): require_once('D:\\www\\saotn.or...') #4 D:\www\saotn.org\www\wp-includes\template.php(496): load_template('D:\\www\\saotn.or...', true) #5 D:\www\saotn.org\www\wp-includes\general-template.php(45): locate_template(Array, true) #6 D:\www\saotn.org\www\wp-content\themes\enfold\single.php(7): get_header() #7 D:\www\saotn.org\www\wp-includes\template-loader.php(75): include('D:\\www\\saotn.or...') #8 D:\www\saotn.org\www\wp-blog-header.php(16): require_once('D:\\www\\saotn.or...') #9 D:\www\saotn.org\www\index.php(17): require('D:\\www\\saotn.or...') #10 {main} in D:\www\saotn.org\www\wp-content\themes\enfold\framework\php\class-style-generator.php on line 123
This post/bug report is mostly an FYI, since PHP 7 is coming soon and Enfold doesn’t seems ready for it. It’ll be nice to have it fixed “now”, but not necessary. I’ve reverted back to PHP 5.5 (due to a bug in WinCache for PHP 5.6). I’m more than happy to provide more debug information if needed.
Debugging Info for Theme support: Theme: Enfold Version: 3.2 Installed: enfold AviaFramework Version: 2.2 AviaBuilder Version: 0.8 ML:256-PU:14-PLA:9 WP:4.3-alpha-33039 Updates: enabled
-
AuthorPosts