When saving this page it is crashing the server. Error "httpd application quit unexpectedly"

the error is 2006-12-12 16:45:51 -0500

EXC_BAD_ACCESS (0x0001)
KERN_PROTECTION_FAILURE (0x0002) at 0x00000049

Thread 0 Crashed:
0 call_user_function_ex + 88 (zend_execute_API.c:443)
1 array_user_compare + 104 (array.c:542)
2 zend_qsort + 200 (zend_qsort.c:86)
3 zend_hash_sort + 188 (zend_hash.c:1150)
4 zif_usort + 264 (array.c:585)
5 get_module + 54668
6 zend_oe + 15836
7 zend_oe + 16480
8 zend_oe + 16480
9 zend_oe + 16480

We are running on Mac OSX - Apache/2.0.59 (Unix) PHP/4.4.4 DAV/2 mod_ssl/2.0.59 OpenSSL/0.9.7l

____________________________________________________

When trying to save a file (admin/settings/content-types/quickfile) we are getting the "file path to this quickfile" error like many others have experienced. It does not matter in our case if the directory is in the public path or not.

____________________________________________________

I am unclear on where to get the data for the PDT Token field. We are using the Sandbox.

I am using clean URLs etc and have tried all the other suggestions in previous posts.

Thanks

Chris

Comments

old_mac’s picture

The quickfile tables are not getting written to the database, when the module is activated which explains a lot!

admin>modules>activate

Chris

alexis’s picture

Hello, I can't reproduce the problem because I don't have a Mac available, but just installed the module in a Linux Fedora Core 5 server and created the tables with no problem at all.

Please take a look at the other issues for this module, one of them explained quite clearly where to get the Paypal token.

Regards.

old_mac’s picture

OK..I have done a complete new install of Drupal 4.7, on a new server and db. The only module that was added is the quickfile.

This is what is happening...all URLs are clean

1. home>create content>quickfile ERROR: File path not found
We have tried the directory inside and outside the public path. No change.

2. administer>quickfiles. Save configuration is not written to mySQL

3. administer>quickfiles> paypal. Save configuration is not written to mySQL

4. administer » settings » content types >configure. Save configuration crashes the server as mentioned before.

Cheers

alexis’s picture

Assigned: Unassigned » alexis
Status: Active » Postponed (maintainer needs more info)

Please write the path you are entering for your quickfiles.

Are you still running on Mac?

old_mac’s picture

/Applications/MAMP/htdocs/quickfiles/

I had a look at the code and I'm uncertain about the autocomplete function. The defaults mean nothing on the Mac/Unix.

alexis’s picture

You are right, many things are different between file systems of different operating systems. I've just worked with Linux and I'm not sure about the changes needed to run in Mac. If you can correct the code to work with Mac would be great.

old_mac’s picture

I tried this with PHP 5, drupal 5.2 and a clean install of Quickfile for Drupal 5.1. It acts very much the same as the other version.(4.7)

The only way to get it to save a quickfile is to set the path to the file to "/".

I also found that the autocomplete is causing a problem. Here is the error.

"warning: Missing argument 1 for quickfile_file_autocomplete() in /Applications/MAMP/htdocs/drupal5/modules/quickfile/quickfile.module on line 2878."

I will have a look at the code to see what I can find and let you know...

Chris

old_mac’s picture

The major problem is the autocomplete. Why does each quickfile have this field anyway. Paths are set once in the quickfile config anyways.

The default directories "home/user/quickfile" etc means nothing on most servers.
I tried this on our Linux ISP server and we see the same problems with paths.

Our currency is set to CAD, and it is saved that way in mySQL, but it always defaults to US$25.00

duaelfr’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

This version of Quickfile is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.