[Solved] Error in v3.2.2: ^SUCCESS$" was not found in the response body. [Solved] Error in v3.2.2: ^SUCCESS$" was not found in the response body.
 

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Main Menu

[Solved] Error in v3.2.2: ^SUCCESS$" was not found in the response body.

Started by levorto, July 12, 2008, 11:33:31 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

levorto

Hi Etienne.

I really hope you can help... I don't understand it, but it seems like I have the $SUCCESS string problem - atleast I think thats the problem...

Your java plugin seems like an exceptionally good and well-thought plugin,
and it really suits my site's needs (lots of pictures), so I hope that you can help me ...  ???


Here's the debug (looks like an exhaust error too?): I've added it to an .txt file due to the max allowed characters error

http://broesby.dk/galleri/DebugSUCCESSStringError.txt

(edit: I've tested your test gallery first - I can easily upload a picture there, so its a serverside problem)

etienne_sf

Hi,

  The real error is:
11:20:40.599 [DEBUG] Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 282128 bytes) in /mounted-storage/home98c/sub003/sc61581-GLWZ/www/galleri/include/functions.inc.php on line 2040\r\n

It seems like the applet, when it reduces the picture size, can generate pictures that doesn't work.

It's the same error as in the thread below (      Upload not working, memory exhausted and problems with user gallery).
http://forum.coppermine-gallery.net/index.php?topic=53710.0

  DFF gave me an admin account on a test forum. But I did not have time to work on it.


Etienne

DFF


etienne_sf

Quote from: DFF on July 13, 2008, 09:43:14 AM
Same host, so maybe it has something to do with this?

Probably.

  I'll try to find out a workaround...

Etienne

etienne_sf

Please see the release 3.2.3.

  It corrects this error.

Etienne