The update to V3.0 promptly disabled all my shopp ecommerce products and pages.
Also will not enable a plugin on a specific page; already disabled in global plugins.
After updating to WP 3.5.2, rolling back to the previous version of this plugin won’t work for me anymore either.
My only option now is to disable the plugin – until these problems get fixed by the author.
Been a really useful plugin – that is until latest update for this plugin & WP.
What I’m saying is that if the array was not pulled properly r inserted properly there would be no plugins disabled or enabled at all. Its all or nothing. If you try to remove some characters from the serialized array string then PHP can’t construct it back to an array unless you find the index numbers and change them to match the character and position counts. I’m saying none of this makes any sense and I have no idea how you only got some of your plugins imported but not others.
Well, I wish I was a programmer :), I have no idea as well. Every new PO update in the past did not give me any major issue. This new one which is a total redesign has obviously affected many in different ways.
I’m sure the answer is there, just hasn’t been seen yet. I don’t know how I can help, maybe send you the SQL table to see ?
In the meantime, I’l just use the old version, until it is solved or finally breaks down with a new WordPress version that is incompatible.
Can you give me temporary access so I can take a look at it?
Ok, will send you the wordpress details later.
Does it have something to do with the wordpress installation being in a subfolder ? Ours is like this :
The blog is in astrablog …
I have logged into your admin and tried to get the plugin working but I’m seeing an issue. I installed debug queries so that i could see what queries were being done. The one to retrieve your disabled and enabled plugins looks like this:
SELECT bj2_posts.ID FROM bj2_posts INNER JOIN bj2_postmeta ON (bj2_posts.ID = bj2_postmeta.post_id) WHERE 1=1 AND bj2_posts.post_type IN (‘post’, ‘page’, ‘plugin_filter’) AND (bj2_posts.post_status = ‘publish’) AND ( (bj2_postmeta.meta_key = ‘_PO_permalink’ AND CAST(bj2_postmeta.meta_value AS CHAR) LIKE ‘%\\%www.lusanbidets.com/our-warranty/sitemap/%’) ) GROUP BY bj2_posts.ID ORDER BY bj2_posts.post_date DESC LIMIT 0, 5
Now this isn’t the query I’m performing. The string I send into the get_posts call is %www.lusanbidets.com/our-warranty/sitemap/. Something is adding % and escaping the % i send in.
The latest version fixes the added % which was being done by get_posts. But your products still aren’t showing up. I can completely delete plugin organizer and your products still won’t work so I don’t think that is related to plugin organizer. I did get your sitemap page working as expected though with version 3.0.3.
Ok I got your products working now as well. Shopp needed to be moved to load first. Another plugin was calling session_start which causes Shopp to fail. Now that it loads first it works.
So make sure to upgrade your live site to plugin organizer 3.0.3 and then move Shopp to load first.
I tried to send the information to your Contact Form, but I can’t get past the Captcha code, it also does not seem to work. Tried several times.
Maybe you can email me at info @ astrasuite.com
and I’ll reply back … thanks
Lol. I know its long. But it does work. I get past it every time I log into my site. I’ll send you an email.
Thanks for looking at our Shopp problem Jeff.
I spent some time trying to figure out which file you had changed in order to move the plugin load order – until I twigged: THIS IS ALSO A FUNCTION OF PLUGIN ORGANIZER!
For other people like me that haven’t realised this:
Along with that slick drag-and-drop plugins interface; you will also see a new option available under the drop-down tab: ‘Bulk Actions’ – Save plugin load order.
Just drag and drop to your heart’s content, then select ‘Save plugin load order’, then click ‘Apply’.
Bingo! Saves the new load order to your database!
Now; as long as Plugin Organizer loads AFTER Shopp – all is good!
Very useful for getting any other troublesome plugins to play nicely together.
Your plugin is so useful Jeff, I’m going to add another post about exactly why people with lots of plugins should be also using this one.
My only whinge about the update: I don’t like the settings for the plugin being in a different place – but I guess you had a reason.
After upgrading your test site to plugin organizer 3.0.3 everything seems to work. I disabled w3cache and the AddToAny plugin and they were both disabled when I viewed the page. It was probably related to the issue I fixed with 3.0.3.
It looks like the PO settings got carried over this time …
But take a look at this :
You can see shortcodes there. Inside the post, they are correctly marked as activated. If I edit the post and save without touching anything, then it gets corrected and will be displayed properly, like in this other one (no shortcodes showing):
I have W3 cache off, I have cleared all caches, etc.
What do you think is the problem ?
Once you have seen the above, maybe I can try to restore all and update with W3 cache off ? I never had to disable W3TC before though.
It’s like the PO settings are there, but the post needs to be edited and saved to get the post to show as expected.
* If it might help, some more information:
The plugin for those shortcodes are deactivated under Global plugins, and only activated in these posts shown above.
For Nextgen plugin, which is not globally deactivated, it does work as expected.
Another example, for Contact Form plugin, it is globally deactivated, and it does not work as expected in a Contact form page I made for it (shortcode showing):
I just looked again, one hour after I posted the above, all are fine now *scratch head*, I didn’t do anything.
I found a typo that imported the old permalinks into a custom field called _PO_post_permalink. It should have been _PO_permalink. I fixed the site for you and fixed the typo in version 3.0.4. I also included code to fix the problem on anyone’s site who has already upgraded with the typo in the code.
- The topic ‘Update no good with Shopp ecommerce website.’ is closed to new replies.