Forum Replies Created
-
Posts
-
I have tested SymbiostockPro with the following WooCommerce versions: 6.2, 6.8 and 7.1 – each with PHP7.4 (FPM by Apache) and ImageMagick7.1 – so far it works without errors.
SymbiostockPro currently does not work with PHP8.0 and PHP 8.1. Unfortunately I don’t have enough experience to investigate what the problem is.
There is a sepate update/test for the Symbiostock Express:
https://www.symbiostock.org/forums/topic/symbiostock-express-compatibility-with-woocommerce-7-1/@robin, are you still updating the plugin for future PHP versions?
hello – generating thumbnails actually doesn’t have much to do with wp-rocket. it’s just how they are managed under wordpress. there are many plugins and settings here that can optimize them.
On the subject of wp-rocket, I have very good experience – as long as the product page does not need to be generated dynamically. Then wp-rockjet can generate a static html page. this relieves the server noticeably after a short time. and the delivery of the page is really faster!
but it is clear that wp-rocket always clears the cache when e.g. plugin-updates are installed. or something is changed on wp-rocket.
by the way css-minify and javascript deferred works well for me. a CDN is certainly also good – but the real boost comes from caching.
I think Symbiostock is not the problem in most cases of updates. I have 2 sites with Symbiostock at the moment. One runs with WooCommerce 6.6 the other with 6.3 … but I can run the server only php-fpm 7.3 (Apache). Fast-cgi or nginx do not work. exactly here I had problems after the update.
Thanks for the suggestion – I’ve also had the idea of using some sort of parent property. For example, you could filter first by print and digital download version and then query the sizes.
But there are 2 points that are important – on the one hand an additional click always reduces the conversion rate. On the other hand, many sublicenses would burden the wordpress table – purely technically, this would probably be enjoyed with caution or a limit is recommended.
But I am not a developer and can only report from a user perspective.
yes – WC 4.9.3 is the latest who is running without errors – an update to Woocommerce >5.0 changes the database and this wouldn’t work. (also on my sites)
yes – on this page and Symbiostock also prints errors on the WordPress admin page when an order cannot be processed or when files are corrupted. do you also use Woocommerce < 5.0?
ok, fine – Apache is fine. I’m wondering that you did not get any errors in the reporting when you manually start the cron job? ..because the cron job should try to process orders when they have ‘processing’ status. but I do not have an idea if you can check what happens maybe with any other php-log. you could also test if the system is able to send mails. .. now my ideas are running out.
you can manually start the cron job by ‘Run now’ on top of the settings page.
Hello, … correct is: the cronjob must do the task. To find out what the problem is, you could check that in the Symbiostock Settings / Downloads / Autocomplete Orders is on. Force download is on. and in Settings/ System / Processor Error Reporting is on. … also it would be good to know if you are using PHP Apache or Nginx and if you are hosting or running a server yourself.
Thanks Robin and Chris for the info. As for the WooCommerce settings, I can’t find a way to change the OutofStock status as the initial setting for the non-digital licenses. Chris, the settings you mentioned only concern frontend settings.
I also understand WooCommerce so that he waits until a specification of the inventory is made. If I let WooCommerce publish the products a second time without further settings to change – all products are ‘InStock’.
… the same must happen again after a price change to a Symbio license, which is just a bit cumbersome.
Hi Robin, thanks for the feedback – i also waiting with excitement for the update!
i use Symbiostock not only for digital downloads – i also use it for a print-on-demand store. The licenses are print sizes there and it already works very well.
But there is a problem with the workflow. It’s that after uploading and processing the images, Symbiostock initially ‘out-of-stocks’ the products that are not offered as digital downloads. This is not so bad, because I still add meta information, such as SEO data and then change the products to ‘InStock’ with the import-export plugin.
But if now, e.g. a price change on the licenses takes place and the CronJob updates the products, it sets the status back to ‘OutofStock’ – i.e. after each update by the Symbiostock CronJob I have to update the products again with the Import-Export Plugin.
Could the workflow be adjusted again here with an update? In my opinion, the ‘Out-of-Stock’ status is obsolete. And from your point of view, would it be possible to manage a second level of licenses via Symbiostock in addition to the first?
Hello Robin,
I think an update is probably necessary. Due to the last security update at WooCommerce, many plugins have stopped supporting versions of WC below 5.x. Here in Germany, for example, the very important plugin German Market (requires WC 5.1.x), whereby the legal security of the store is no longer guaranteed. But also e.g. Facebook Pixel.
Although Symbiostock works with the security update to WooCommerce 4.9.3 … in my case, when I update WooCommerce to above 5.x and update the database, the Symbiostock/Cron jobs no longer work.
Currently WooCommerce is already at version 5.6. When can we expect a Symbiostock update for a current WooCommerce version?
it looks like you already have a WooCommerce store running on the domain. If you want to create a store for digital downloads, i would recommend to create the ImageBank as a subdomain to offer digital downloads only. You can also run both domains with one installation, but that means some extra work and it has some limitations.
If you want a offer, please write me with an estimation how much storage space is needed for original videos & photos. An installation can be done in 2-4 weeks.
Kindly,
KnutI speak only for myself but I think it is difficult to convey to the customer that after a purchase is made, the conditions change. If you change the download expiry, the change should affect all future orders and always applies to all Symbio products.
i also have the same problem on my server with a new installation. I have changed the following data for the ImageMagick-6/policy.xml – besides the read & write permissions I increased the memory allocation in particular – it worked with that:
<policymap>
<!– <policy domain=”system” name=”shred” value=”2″/> –>
<!– <policy domain=”system” name=”precision” value=”6″/> –>
<!– <policy domain=”system” name=”memory-map” value=”anonymous”/> –>
<!– <policy domain=”system” name=”max-memory-request” value=”256MiB”/> –>
<policy domain=”resource” name=”temporary-path” value=”/tmp”/>
<policy domain=”resource” name=”memory” value=”2GB”/>
<policy domain=”resource” name=”map” value=”4GB”/>
<policy domain=”resource” name=”width” value=”512KP”/>
<policy domain=”resource” name=”height” value=”512KP”/>
<!– <policy domain=”resource” name=”list-length” value=”128″/> –>
<policy domain=”resource” name=”area” value=”128MB”/>
<policy domain=”resource” name=”disk” value=”2GiB”/>
<!– <policy domain=”resource” name=”file” value=”768″/> –>
<!– <policy domain=”resource” name=”thread” value=”4″/> –>
<!– <policy domain=”resource” name=”throttle” value=”0″/> –>
<!– <policy domain=”resource” name=”time” value=”3600″/> –>
<!– <policy domain=”coder” rights=”none” pattern=”MVG” /> –>
<!– <policy domain=”module” rights=”none” pattern=”{PS,PDF,XPS}” /> –>
<!– <policy domain=”delegate” rights=”none” pattern=”HTTPS” /> –>
<!– <policy domain=”path” rights=”none” pattern=”@*” /> –>
<!– <policy domain=”cache” name=”memory-map” value=”anonymous”/> –>
<!– <policy domain=”cache” name=”synchronize” value=”True”/> –>
<!– <policy domain=”cache” name=”shared-secret” value=”passphrase” stealth=”true”/> –>
<!– <policy domain=”system” name=”pixel-cache-memory” value=”anonymous”/> –>
<!– <policy domain=”system” name=”shred” value=”2″/> –>
<!– <policy domain=”system” name=”precision” value=”6″/> –>
<!– not needed due to the need to use explicitly by mvg: –>
<!– <policy domain=”delegate” rights=”none” pattern=”MVG” /> –>
<!– use curl –>
<policy domain=”delegate” rights=”none” pattern=”URL” />
<policy domain=”delegate” rights=”none” pattern=”HTTPS” />
<policy domain=”delegate” rights=”none” pattern=”HTTP” />
<!– in order to avoid to get image with password text –>
<policy domain=”path” rights=”none” pattern=”@*”/>
<!– disable ghostscript format types –>
<policy domain=”coder” rights=”read|write” pattern=”PS” />
<policy domain=”coder” rights=”read|write” pattern=”PS2″ />
<policy domain=”coder” rights=”read|write” pattern=”PS3″ />
<policy domain=”coder” rights=”read|write” pattern=”EPS” />
<policy domain=”coder” rights=”read|write” pattern=”PDF” />
<policy domain=”coder” rights=”read|write” pattern=”XPS” />
</policymap>Hi Sergey, I fixed this problem after deleting the css code in the browser and server caches.
with kind regards
