AjaxSearch 1.9.0 Final release now available

I set the directory to be writeable but still didn’t work because that log file doesn’t exist.

Did you clear the cache before to redo ? Are you sure you didn’t get the previous message ?

I have re-installed the last svn version of ajaxSearch with Evo1.0.4 and I generate the log file when the directory is writeable.

I cleared the cache - still the same error - what directory has to be writeable? - is it the snippets/ajaxSearch/classes directory?

what directory has to be writeable? - is it the snippets/ajaxSearch/classes directory?

No, the log file is created inside assets/snippets/ajaxSearch directory

Maybe it would be better for AjaxSearch to put its log file in a directory that is writable under all server configurations, such as the assets/cache directory? That way nobody would have to modify the permissions of their installation.

Quote from: sottwell at May 25, 2010, 06:13 AM

Maybe it would be better for AjaxSearch to put its log file in a directory that is writable under all server configurations, such as the assets/cache directory? That way nobody would have to modify the permissions of their installation.

I 2nd that one

Maybe it would be better for AjaxSearch to put its log file in a directory that is writable under all server configurations, such as the assets/cache directory?

My first anwser was to reply: you are right.
But why in cache directory, why not in export directory or an other directory. In fact, I think that’s better to keep this log file related to AjaxSearch in the ajaxSearch directory.

The debug parameter shouldn’t normally used in production. In normal case, for performance reasons, it should be always set to 0. The issue encontered by mmjaeger was due to a wrong initialisation.

So I prefer change the documentation and the code as follow:
- create a directory ajaxSearch/debug
- improve the documentation around the use of this parameter:
Not used for production. The log file is created in the ajaxSearch/debug directory and should be a writable directory.
- when running the snippet, if this directory is not writeable display an alert message: "your ajaxSearch/debug should be writeable".

Quote from: coroico at May 25, 2010, 07:22 AM

Maybe it would be better for AjaxSearch to put its log file in a directory that is writable under all server configurations, such as the assets/cache directory?

My first anwser was to reply: you are right.
But why in cache directory, why not in export directory or an other directory. In fact, I think that’s better to keep this log file related to AjaxSearch in the ajaxSearch directory.

The debug parameter shouldn’t normally used in production. In normal case, for performance reasons, it should be always set to 0. The issue encontered by mmjaeger was due to a wrong initialisation.

So I prefer change the documentation and the code as follow:
- create a directory ajaxSearch/debug
- improve the documentation around the use of this parameter:
Not used for production. The log file is created in the ajaxSearch/debug directory and should be a writable directory.
- when running the snippet, if this directory is not writeable display an alert message: "your ajaxSearch/debug should be writeable".

sounds good to me.

That sounds quite reasonable as an approach coroico.

Ah, I wasn’t aware the log creation was a special case. Certainly anyone wanting to enable the special case should be able to deal with making the directory writable!

Updates around &debug discussed in the previous are now implemented.

Available with the package AjaxSearch190_6880. You could download it from SVN or from this page.