--
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
a few things to check:- make sure filestore is writable (this shows in the installation check, so I'm assuming this is OK)
In config.php:- check to see if your file extensions are included in $no_preview_extensions
- check to see if $enable_thumbnail_creation_on_upload = true (this is the default, but if it's set to false you need to run create_preview.php to generate previews for recently uploaded images)
Do you use watermarks? Are all images set to be restricted? If yes then verify your path to the watermark is correct
--
you need to check for those config settings in config.php NOT config.default.php.
I would try using imagemagick from the command line and see if you get any errors.
--
I did not mean to imply that you were a novice at anything. However, it is not enough to look at config.default.php for those settings, as they are overwritten by the settings in config.php.
have you tried to convert an image via the command line?
have you checked your error logs?
--
you can check php's log, and i'd check the system log as well
One thing to keep in mind is that staticsync runs from the command
line or the task scheduler, whereas images uploaded through the web
interface are created under the user that is running the web server.
So there are two different security contexts involved. If one has
access to the filestore and the other doesn't, this could cause a
problem.
You might figure out what user the staticsync script is running under,
start a command line session as that user, and then verify that you
can save copy files to the filestore.
If you enable
# Log developer debug information to the debug log (filestore/tmp/debug.txt)?
$debug_log=true;
The system will create a debugging log in your filestore temp folder.
You can do this, run staticsync, and then examine the log file. Among
other things, it will log the actual commands sent to the command line
to execute imagemagick. You can then try running these yourself from
the command line to see if they work. If not, you may get more helpful
errors back that would point to the source of the problem.
Look for lines that start
CLI command:
and
CLI output:
or
CLI errors:
Look for lines that start
CLI command:
and
CLI output:
or
CLI errors:
Out of curiosity, is your database configured as Latin1 or UTF-8? We had terrible trouble with special characters until we converted our database to UTF-8. The default in mySQL is Latin1, and sadly there remains no mention of this in the RS documentation.
I don't know if it will fix your problem with Staticsync or not, but your mention of umlauts reminded me of my experience with this. The utf8 designation in config.php doesn't change the character set of your mySQL database.A shot in the dark (from a user, not a developer), but I'm just trying to be helpful.
Doesn't matter whether you're a dev or not, we appreciate it.A workaround would be to disable mysql_charset during the staticsync run and enabling it once everything is in place, but that's hardly a feasible workflow to show RS's capabilities.
Anyways, thank you for the suggestion (I should have mentioned that we already tried that). But as I said, every bit of information is appreciated.
I had a similar problem on a unix install a while back, and it turned out to be related to how ResourceSpace forms the conversion command line in the case of non-ascii characters, or in how the conversion utility read its command line arguments. If memory serves, I added a bit of debug to run_command in include/general.php so that I could see what commands were being run to confirm that was the problem. It was something along the lines of if ( posix_isatty(STDERR) ) { fwrite(STDERR,$command);}To fix it, in image_processing.php I created a hard link to the actual file, but using a temporary ascii filename, making sure to keep the extension the same. Then I passed the temporary file instead for conversion.It might not be the problem you're seeing, but I hope this helps!
I made a lot of use of batch/create_previews.php to recreate the missing thumbs, after disabling the threading, which did not work well for me.
I posted about this a while back and experienced exactly the same problems as you with umlauts:
ghostscript and staticsync- pdf previews are generated when uploading files by java upload because the file path is scrambled. However when files are imported via static sync it breaks when it encounters an umlaut. I am assuming the problems lie with RS (or perhaps, my installation of RS) as Ghostscript is supposed to support UTF-8 (or at least that's what I read; I have not tested this).Comparing the debug output, with mysql_charset="UTF8" set to on vs off, it breaks at the following points:- SQL: select file_path value from resource where ref='1' etc- SQL: update resource set preview_tweaks (i.e. just before GS is supposed to start)- it seems to think file source is: filestore/1_[etc]/1_[etc].pdf (i.e. that the file has been ingested, when in actual fact there is nothing in that folder)
With mysql_charset commented out, GS breaks when trying to create previews, e.g.:- 'PDF multi page preview [....] /var/www/Analysis/hpihh/dradio.pdf', even though it recognises that: 'file source is var/www/Analysis/hpäihh/dradio.pdf'
Hi everyone,
We are evaluating RS for internal usage (within our network) so we set up a test box for this (Win7 x86, IIS7,5) but we ran into a strange issue. No Previews, thumbs other than the place holder graphic. We have absolutely no idea why it isn't working.
Our installtion process followed the wiki article for installation in win7 32 bit.
We have the filestore in:
C:\inetpub\wwwroot\resourcespace\filestore
Our syncdir is in:
C:\Pictures (this is just for the test setup)
Our folder matching is working as desired, we run staticsync through CLI.
The folders are read and all our desired fields are populated as expected.
BUT, there are NO preview-images, thumbs nothing besides the fields... all it shows is the placeholder graphic for missing files
I don't really know what's going on and need help. We've been hunting through the group for close to a day with now viable clue.
The installation check gives an error for ffmpeg, however I thought that doesn't affect us, since we're only working with graphics for now.
The error is as follows:
" Unexpected output when executing "c:/ffmpeg/bin\ffmpeg.exe" -version command. Output was ''. "
Everything else is ok, at least the check isn't telling anything other than the described error.
Do you have an idea what could be wrong?
t.i.a.