phpwcms Support Forum

Hi , I get 2 errors in the backend when I try to upload picture in content part:

error while updating content: UPDATE phpwcms_articlecontent SET acontent_aid = '324', acontent_uid = '1', acontent_title = '', acontent_subtitle = '', acontent_type = '1', acontent_sorting = '10', acontent_visible = '1', acontent_before = '', acontent_after = '', acontent_top = '0', acontent_block = 'CONTENT', acontent_anchor = '0', acontent_text ='

Then apear the text in the content part and after another error:

', acontent_image ='1805:logo.gif:2708c5e9be75423e6c8fb08933338abb:gif:120:::1:0' WHERE acontent_id=467 AND acontent_aid=324

maybe this two are only one:

error while updating content: UPDATE phpwcms_articlecontent SET acontent_aid = '324', acontent_uid = '1', acontent_title = '', acontent_subtitle = '', acontent_type = '1', acontent_sorting = '10', acontent_visible = '1', acontent_before = '', acontent_after = '', acontent_top = '0', acontent_block = 'CONTENT', acontent_anchor = '0', acontent_text ='', acontent_image ='1805:logo.gif:2708c5e9be75423e6c8fb08933338abb:gif:120:::1:0' WHERE acontent_id=467 AND acontent_aid=324

this have apear after I restore the website after a transfer

http://forum.phpwcms.org/viewtopic.php? ... ontent+SET

EDIT: too late - need more coffee

BTW: there is a lovely but shy search function at the uppermost right corner of the forum page
BUT: we are all really greedy searchers and finders so we will do it for you, of course (but only for you )
HEY: coffee is doing it's duty

when we are ready with our eduacation we got to work as SEARCH BOTS !

Hi, thanks you for that but I don't see how that information for my problem, I have this problem when I try to use 1 picture in the article from the Files, I did not try to add a script in the content

to clarify: try to run the sql updates and the error(s) should go away...
At least this is the meaning (and opinion) of the content of my mentioned post

ok and how do I do that ...

and another problem in 1 of my websites that runs on 1.2.6 - both errors apears in this phpwcms 1.2.6 :

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 6688 bytes) in /home/stephany/public_html/include/inc_ext/ss_image/ss_image.class.php on line 84

I have search the forum find what they advise but is not working ... I try this:
http://forum.phpwcms.org/viewtopic.php? ... 8a6#p90238

I have put in the php ini and hattcess and is not working every time I try to ipload a jpg file I get this error, with gif files no problem.

the error si self-explaining !

Image needs more memory for recalculating as there is reserved in php.ini

Thats all, make it smaller and it will run into the system.

the image have 230 kb

says nothing.. f.e. it is 1800x1800 pixels or so and then php cannot serve the needed memory.. OK ?

picture have 1200x824

not alone file size may be one issue but --> especially for jpg:
--> dimensions, resolution??? 72dpi will be sufficient, color mode RBG but not CMYK, LAB etc....

you might also know from experience that JPG is a compression format for images to reduce file size for saved files. Opening files to e.g. display or editing (that is was GD or ImageMagick do!) requires more RAM (than you might think because smaller file size {when saved}. It needs much more RAM --> really plenty of RAM to open a JPG-file --> that DOES NOT FIT COMMON INTERNET STANDARDS.
To defend the server from being out of memory these scripts STOP EXECUTING --> will do no resize and so on....

So, my advice: check your images....

culda_a wrote:...this have apear after I restore the website after a transfer

or you DB just didn't survive -- this would be something we couldn't solve....

any backups available??? --> upload again || tested locally before being public again??? --> XAMPP, LAMP, MAMP

the problem with the image is solved but I have this error when I try to save any article:

Did you really run every sql update after an (eventually done) update?
Or did you delete the "bad" pictures before continuing?
So many questions, so few answers... yet