June 14, 2012 at 5:27 am #13265
Updated to WordPress 3.4 now showing errors:
get_theme_data is deprecated since version 3.4! Use wp_get_theme() instead
Could you help?June 14, 2012 at 8:20 am #78495
In propulsionframeworkphpinc-autoconfig.php replace:
$avia_base_data = get_theme_data( AVIA_BASE . '/style.css' );
$avia_base_data = wp_get_theme( AVIA_BASE . '/style.css' );
I’ll notify Kriesi about the warning message.June 14, 2012 at 12:03 pm #78496
When I replace the above, the site completely changes, it shows the propulsion demo template, only with my content.June 15, 2012 at 3:50 am #78497
Kriesi has been flagged to this thread so he can take a look. Let us know if you have other issues.
MyaJune 15, 2012 at 7:54 am #78498
As a temporary fix you can hide the warning messages – see: http://codex.wordpress.org/Editing_wp-config.php#Debug
PeterJune 15, 2012 at 12:17 pm #78499June 15, 2012 at 4:05 pm #78500
If you have any additional issues with the update, let us know ASAP. I’ve updated my test live installation and will hopefully have all the bugs reported in the next week to Kriesi as wel :)
DevinJune 18, 2012 at 3:56 pm #78502
So now I’ve noticed the images for the sideshow appear only for a second then you only see the load progress. Is there a remedy for this?
I’ve already updated all the plugins.
ThxJune 18, 2012 at 6:02 pm #78503
Do you have a link to the site where we can take a look? I’m not running into the same issue with any of my Propulsion sites so far.
DevinJune 18, 2012 at 6:58 pm #78504June 19, 2012 at 5:40 pm #78505June 20, 2012 at 4:46 pm #78506
Can you try disabling your plugins and using the most recent version of the theme. There might be a conflict with one of the plugins running as well as issues with the 1.2 version of theme in WP3.4.
DevinJune 21, 2012 at 5:24 am #78507
I tried to disable but nothing happened, still not showing slideshow images.
ThxJune 21, 2012 at 6:08 am #78508
Kriesi will release an update in the next few days which will fix this warning message.
PeterJune 26, 2012 at 5:12 am #78509June 26, 2012 at 5:21 am #78510
Hopefully within the next couple of weeks if not sooner. Once Kriesi is done with the updates ThemeForest must review so there’s a bit of waiting period.
MyaJune 26, 2012 at 10:10 am #78511
Interesting, according to Kriesi’s Facebook page and Twitter, Propulsion is updated 1 day ago to ver. 1.4, so I downloaded it from ThemeForest.
In version.rtf I see 1.4 but when you open style.css there are still 1.3.2
RegardsJune 26, 2012 at 10:39 pm #78512
So is the update ready according to VBM. If it’s going to take a couple of weeks, is there a work around for me, currently none of my sideshow images appear?
ThxJune 27, 2012 at 3:41 am #78513
I’ve updated the new files for the new release but still the slide show doesn’t work. Any suggestions?
ThxJune 27, 2012 at 8:20 am #78514
so … is Propulsion updated to 1.4 or not? according to FB and Twitter it is.
Why is still version 1.3.2 in style.css in ThemeForest download and 1.4 in version.rtf, did you miss to update some more files maybe, not just style.css?June 27, 2012 at 10:38 am #78515
@VBM – no. I checked my files and it seems like Kriesi forgot to update the version number in style.css (it still says 1.3.2 instead of 1.4). However if version.rtf contains the change log for 1.4 you’ve the right (and updated files).
@O5 try to deactivate all plugins – probably one causes a js error.June 27, 2012 at 4:17 pm #78516
I’ve found the conflict, it’s a result of using the code at this link http://www.kriesi.at/support/topic/disable-mobile-menu-regular-menu-instead-of-drop-down#post-53419
Apparently when the select a page drop down is disabled it throws off slide show. Any way to still disable select a page drop down for mobile devices without causing problems with slide show?
ThxJuly 4, 2012 at 6:34 am #78517
Can you post a link to your website please – I’d like to debug the js error myself. To be honest I’m pretty sure that something else causes the js error.
PeterJuly 5, 2012 at 3:58 am #78518July 5, 2012 at 5:12 am #78519
The topic ‘Updated to WordPress 3.4 now showing errors…’ is closed to new replies.