Wednesday 04 February 2004 11:34:42 am

Nice idea, Emil!

Something from me:

LARGE FILES:
When you have problems uploading large file, check the php.ini settings (there are two, that are usually set to 8M or so)
When you have problems indexing large file (binary file indexing), use the current ez 3.3 release, which has some fixes and optimizations for it. Note: as the order of words is stored (for phrase searching, i guess), you will get one DB table entry for every single word (occurance) in a document. That means: if you have a manual with 30.000 words, you will get 30.000 entries in the db table.

IMAGEMAGICK ISSUES:
We found some problems with converting JPGS with imagemagick's convert (an old version, but...). Most jpegs work, some do not work. If you experience this (or other ImageMagick issues, ie. installing it at all), you should go for GD2. My test gave nice results. GD works (using PHP 4.3.3 and GD 2.0.x), converts every JPG, is faster then Convert and knows the basic filters, including grayscale. It does not support "border" (judging from the gallery demo).

Using FTP for changing Templates:
When you use FTP to upload/change templates (ie. Dreamweaver), take care of your FTP server settings (user group, UID mask etc), so the webserver user (www, wwwrun, apache, nobody or so) can read and write the templates. You will need "read", so ez can use the templates and "write" permission, so you can change the templates in the admin web interface. If all goes wrong, use an FTP client to change the file permissions to "777" (read and write access for user, group, world). This MAY be a security issue.

Template caching issues:
When you upload/update template files by FTP, ezPublish is not able to notice this. That means, that the template (compile) cache is not updates and you will not "see" your new templates.
You have two options: clear caches in the admin interface (all or at least the template compile and override caches) OR edit the template, that you just uploaded, in the admin interface: Edit is, save it. ez will the clear all necessary files.

Template caching while developing:
While you are developing, you should disable the different caches (template compiling, content caching, cache-blocks). This usually is a sitewide setting, so do not use this for sites in production, when you develop a new "design" or so!
While you are working on the pagelayout.tpl files, you can edit the file without any cache-block blocks. So, pagelayout blocks will not be cached. When you finished the pagelayout design, you should introduce cache-blocks. READ THE DOCS for this, because it's easy to mess up a lot, when you don't understand about the cache-block-keys. On the other side, you should use the cache-blocks for performance reasons.

Hm... Maybe, we should post all this in the docs section...

Marco
http://www.hyperroad-design.com