Images not processing? Here are the most common reasons.

[RobinKeymaster]

Your media is processed by Symbiostock via the processor (Symbiostock > Settings > System). This must be added to your control panel’s cron system (scheduled tasks) to run once every minute. Instructions on doing so are here:

http://www.symbiostock.org/docs/setting-up-the-schedulerimage-processor/

If you have this running and are still encountering issues, proceed.

First, enable error reporting and see if that tells you anything

Before posting about it and asking for help, a quick way to see if you are getting errors is to enable error reporting. Go to your Symbiostock > Settings > System tab and enable error reporting. Then manually run the processor and see if anything odd pops up. Then proceed with diagnosing your issue as normal.

If this provides no input, then edit your wp-config.php and enable debugging by changing this:

define( ‘WP_DEBUG’, false );

to this:

define( ‘WP_DEBUG’, true );

By doing one or both of these methods, you will get any errors being generated by your processor.

Using error reporting and the guides below, please assess your issue using these instructions first. 99% of errors will fall into one of these categories. If after exhausting these possibilities, you cannot find a solution, then post a request.

[RobinKeymaster]

Most common reasons the processor is not running (either manually or via the cron) or not processing media:

You have insufficient memory with your web host.

Symptoms: You run the processor and do not see all the resulting boxes. Once error reporting is enabled you see a memory issue or you see a script timeout error. Both of these are due to your server not being able to handle processing your media.

Solutions: Contact your web-host to upgrade, or move to Symbiostock Hosting.

You have a media file that is corrupted waiting to be processed.

Symptoms: Once error reporting is enabled, you get weird Imagick or GD errors that suggest the media file in question is corrupted. This is preventing the processor from ever getting through the process.

Solutions: Go into your ss_media/new directory and delete the file in question.

You are uploading your new images to the wrong directory via FTP

Symptoms: You upload media via FTP and it does not get processed by the processor. However, when you upload media via the web uploader, it shows up.

Solutions: Under your Symbiostock > Upload Media tab you have the correct path to your upload directory. Disable your cron, upload a file via the web uploader, and hunt for it in your FTP file system. Once you find it, that is where you should be uploading all your new media.

You are running your site through a CDN or cache service to save on bandwidth and increase speed

Symptoms: When you manually run the processor, it tends to work, but the cron does not. There is no easy way to test this problem aside from temporarily disabling the CDN and seeing if the processor starts working. In this case, the cron is being served a cache’d version of the processor which is not triggering the original processor.

Solutions: Disable your CDN for your processor URL, or entirely for your entire site.

Your site is being run through SSL and there is some problem with the way the cron is calling your processor

Symptoms: When you manually run the processor, it tends to work, but the cron does not. There is no easy way to test this problem aside from temporarily disabling SSL or changing your cron URL to non-SSL and seeing if the processor starts working. In this case, you will have to contact your web-host to determine why this is happening.

Solutions: Disable SSL, contact your webhost, or move to Symbiostock Hosting.

[Author]

Posts