0 items - $ 0
- No products in the cart.
This topic contains 3 replies, has 2 voices, and was last updated by 
kevin(Staff) 1 month, 1 week ago.
Viewing 4 posts - 1 through 4 (of 4 total)
-
Posts
-
Over 6 months ago you stated you were working on compatibility with WP 3.5. How is that going? Also, back in January I had to (frustratingly) go to previous WP version just to get this theme going. I need to update to 3.5 so I can use some plugins and you know… be current with new technologies… I am using WooCommerce 2.0.12 for reasons of selling downloadable products. I am getting errors and I believe it is because the theme has not been updated to be compatible with the new WooCommerce.
Please advise if you’re going to resolve some of these issues.
Website: http://www.sacredrevolt.com/shop/
Warning: uasort() [FUNCTION.UASORT]: The argument should be an array in /home/sacredr2/public_html/wp-content/plugins/woocommerce/woocommerce-template.php on line 795
Hi Drew,
The Siso theme is still on the list of themes to be updated. However because of our theme updates being pretty massive it takes quite a lot of time to create them, test them, and make a stable release.
We are updating our themes one by one and we’ve got quite a lot of themes to work on. over the past months we’ve already released a few theme updates, were actively working on more as well as designing new themes since in the end we need to keep the company running.
For now I cannot do much more than say Siso isn’t Woocommerce2.0 compatible yet. However, the error you post is a warning those shouldn’t affect the working of your code. I believe you canturn off whether warnings are shownin the wp-config. For now, I just cannot guarantee that WC2.0 will work completely.
Kevin
I have seen that the store is still functioning which is a good thing.
Do you know how I can keep those errors from showing?
Hi Drew,
This is a wordpress thing rather than a theme thing to turn those off. You’ll need to go to the wp-config file and change some variables in there. If I am not mistaken you’re looking to change it into this.
error_reporting(0);@ini_set('display_errors',0);Viewing 4 posts - 1 through 4 (of 4 total)You must be logged in to reply to this topic.