Forum Replies Created
-
Posts
-
Issue is resolved through this thread:
http://www.symbiostock.org/forums/topic/related-posts-not-working/
Likely your postmeta tables are InnoDB.
To summarize, the issue is related to the specific mySQL version you are using on your server, and the default table type it uses to store data.
Some more info:
I’ve tested this on PLUS and on our independent test server and I cannot reproduce the same issue. Therefore, I have no idea why it is happening.
However, I can confirm that it is NOT theme related. It has something to do with the related posts upgrade.
Still not sure exactly what it is – however, I can confirm that it has something to do with the new related posts update.
For now, do two things to revert back to WooCommerce’s default related posts if you are experiencing this issue:
1) Disable the Symbiostock enhanced search in your Symbiostock > Settings page
2) Clear all WooCommerce transients via WooCommerce > System status > Tools.
Your related posts should then show up, but not be all that related. I’ll update you when I figure out why this may be happening for some of you.
Hard code won’t be as efficient as it isn’t finding the relevant images unless you PHP that into the URL. But still, doesn’t look bad!
Okay, so I went to WooCommerce > System Status > Tools and cleared your transients. This did not fix the issue, and I can confirm that WooCommerce is performing the related posts query. Appears to be theme related. Still looking into it.
So Mark – on your server I disabled the Symbiostock enhanced related products and it still does not show. This means it is completely theme related. Still checking, just letting you know.
Now, I can’t immediately test this, because it’s complicated, but WooCommerce (unfortunately) caches all related product searches and updates it only once every 30 days I think. There is no way to change this without hard coding a change in the WooCommerce core code.
My first assumption is that it has cached the query and is not doing a new query until that expires. Let me see how to clear it and see if that’s the problem.
Looking into it guys
Hey Cristina,
The widget has a bunch of options to alter how it works. I haven’t had a chance to add documentation yet, so it’s not your fault.
The best way to figure out what the different options do is to add it as a widget using the widget admin section then try the different settings to get an idea. You can also disable the descriptions that way (there is a checkbox)
Hey Steve,
I just compared 1.3.4 and 2.0 and the way it checks for imagick is identical. No clue why that would change. I haven’t experienced that issue on any of my test servers, so I would have to assume it’s unique to yours – why that would happen I have no idea.
It uses the:
extension_loaded(‘imagick’)
checker.
http://php.net/manual/en/function.extension-loaded.php
Which should work if Imagick is installed. I’ll ponder it and see if I can think of a reason.
Hi Tobias,
After processing they should no longer be in ‘new’ – they should be in ss_media. They will only remain in ‘new’ if they have failed processing, and will have a prefix attached to them.
As Steve requested, can you explain why this procedure limits the number of files you can upload?
Steve: As I just emailed you, that issue was happening because of your custom function that simplified the checkout fields. Oddly, the same implementation that is now built into Symbiostock 2.0 uses the same function name.
Henri: Thanks for that – I will be using your instructions to update my own site. 🙂
Just disable the importer/exporter Steve – it should not be enabled when not in use.
Hi Tobias,
As Steve has pointed out, everything is database driven and controlled through WordPress. As the ss_media directory serves only as a repository, there is currently no way of organizing data within it via directories.
With Symbiostock 2.0 you can now import Lightroom supplementary categories as well, so that would probably be the best way of organizing your photos. You can upload them all via FTP to ss_media/new and they will get moved into ss_media, organized within Symbiostock in accordance with your category structures.
And of course there are benefits to it being database driven; you can have images in multiple categories, delete categories, add new ones, and you don’t have to do any file moving.
If you can explain the purpose behind keeping them in directories maybe I can give more advice.
Well, you’re right about that – you can only really run it and customize it when it is live. But I suppose there are a couple of things you can do:
1) Run it on a test install to get all the settings right, then export those settings to the live server.
2) Run it on the same install, but in a different directory. Then, whenever you feel you want to work on it, activate that theme and configure it, then revert back when you’re done so that at least most of the time your site is looking the way you want.
There is not yet an awesome way of doing it, and again, I realize the inconvenience, but for future long term upgrades and updates this is going to make it a lot easier to add tweaks and fixes to it.
I think the main point I was trying to make is that you don’t need to upgrade to Symbiostock Express 2.0 for any particular reason. It looks pretty similar, and has a few fixes here and there, but other than that it’s mostly an internal switch to more standardized code. So although you should do it at some point, don’t feel pressured.
This is another situation where I would suggest contacting Henri if you want to know, because he’s already done it as far as I understand it, so he may have tips on how to do it as painlessly as possible.
You can – in fact, the best way to do it is probably to just re-save them in bulk with the rewriting option enabled.
I can’t guarantee anything with the second question, but I personally am going to rename everything. I think in the long run the SEO benefits will outweigh the short term re-indexing cost.