Image editor does not start
Permalink 1 user found helpful
Hi all
I try to edit an image (in the sample website of the concrete5 installation) but the editor does not start. I have this problem in the installation of the provider of my website.
Locally I do some tests within xampp and there, I can use the image editor.
Any idea what could be the problem?
Regards
Matthias
I try to edit an image (in the sample website of the concrete5 installation) but the editor does not start. I have this problem in the installation of the provider of my website.
Locally I do some tests within xampp and there, I can use the image editor.
Any idea what could be the problem?
Regards
Matthias
Do you get any errors in your browser console?
No, there is no message. The editor window does not open, nothing happens. I have to leave the page to get back to normal editing.
Make sure you are on the latest version, which is currently 5.7.2.
Post your environment information Dashboard > System & Settings > Environment > Environment Info.
Ensure there are no error messages in your developer console, press F12 to open the browser developer tools and go to the Console tab.
With no error messages to go by, its really hard to diagnose the problem.
Post your environment information Dashboard > System & Settings > Environment > Environment Info.
Ensure there are no error messages in your developer console, press F12 to open the browser developer tools and go to the Console tab.
With no error messages to go by, its really hard to diagnose the problem.
What browser are you using?
Hi
I use already concrete 5.7.2. The problem has something to do with the environment, e.g. the configuration of the apache webserver. On my local pc the editor works with the same concrete5 version and the same image but on the host of my provider, there is a problem. I use firefox and with the web developer tools, I now see a error message:
Request-URL: http://www.neu....../index.php/tools/required/files/edit?fID=49...
Request-Methode: GET
Status-Code: HTTP/1.1 500 Internal Server Error
Request-Header 21:13:05.000
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Referer:http://www.neu........./index.php/dashboard/files/search...
Host:http://www.neu.........
DNT: 1
Connection: keep-alive
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Accept: */*
Gesendetes Cookie
CONCRETE5: c34f865f0ef95578daf94ac7374d1a83
Response-Header Δ265ms
X-Powered-By: PleskLin
Transfer-Encoding: chunked
Server: Apache
Date: Mon, 03 Nov 2014 20:12:14 GMT
Content-Type: text/plain; charset=UTF-8
Connection: close
I use already concrete 5.7.2. The problem has something to do with the environment, e.g. the configuration of the apache webserver. On my local pc the editor works with the same concrete5 version and the same image but on the host of my provider, there is a problem. I use firefox and with the web developer tools, I now see a error message:
Request-URL: http://www.neu....../index.php/tools/required/files/edit?fID=49...
Request-Methode: GET
Status-Code: HTTP/1.1 500 Internal Server Error
Request-Header 21:13:05.000
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Referer:http://www.neu........./index.php/dashboard/files/search...
Host:http://www.neu.........
DNT: 1
Connection: keep-alive
Accept-Language: de,en-US;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate
Accept: */*
Gesendetes Cookie
CONCRETE5: c34f865f0ef95578daf94ac7374d1a83
Response-Header Δ265ms
X-Powered-By: PleskLin
Transfer-Encoding: chunked
Server: Apache
Date: Mon, 03 Nov 2014 20:12:14 GMT
Content-Type: text/plain; charset=UTF-8
Connection: close
Well, if your provider allow the following, create a simple info.php file inside the root of your website with the following inside:
Then you can access this file:
http://www.example.com/info.php...
And if everything ok you can check how the server it's configured, check if PHP GD it's present and enabled, the Table with this information start with GD Support and must show Enabled
After you check this information delete the file info.php because other people can get sensible information about your configuration. DON'T FORGET
<?php phpinfo(); ?>
Then you can access this file:
http://www.example.com/info.php...
And if everything ok you can check how the server it's configured, check if PHP GD it's present and enabled, the Table with this information start with GD Support and must show Enabled
After you check this information delete the file info.php because other people can get sensible information about your configuration. DON'T FORGET
Thank you. I get
gd
GD Support enabled
GD Version bundled (2.1.0 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.3.11
T1Lib Support enabled
GIF Read Support enabled
GIF Create Support enabled
JPEG Support enabled
libJPEG Version 6b
PNG Support enabled
libPNG Version 1.2.49
WBMP Support enabled
XPM Support enabled
libXpm Version 30411
XBM Support enabled
This looks like gd is ok?
gd
GD Support enabled
GD Version bundled (2.1.0 compatible)
FreeType Support enabled
FreeType Linkage with freetype
FreeType Version 2.3.11
T1Lib Support enabled
GIF Read Support enabled
GIF Create Support enabled
JPEG Support enabled
libJPEG Version 6b
PNG Support enabled
libPNG Version 1.2.49
WBMP Support enabled
XPM Support enabled
libXpm Version 30411
XBM Support enabled
This looks like gd is ok?
Well, can be little hard to find where is the problem.
Maybe you have some upload limit defined in your php.ini?!
Activate the option:
Show the debug error output
System & Settings -> Environment -> Debug Settings -> Display Errors
Maybe can help us to guide you.
Maybe you have some upload limit defined in your php.ini?!
Activate the option:
Show the debug error output
System & Settings -> Environment -> Debug Settings -> Display Errors
Maybe can help us to guide you.
Having the exact same issue. Activating the "Show the debug error output" option produces no output. All I get in the dev console is this:
Where ### is my domain.
Eventually the image editor overlay loads, but just displays "Access Denied" in place of the editor.
PHP GD is present and enabled.
Similarly to tipweb, it works fine on my local LAMP stack under Mac OS 10.8.5, but not on my Digital Ocean stack.
I'm not using a php.ini file, so I'm guess the issue lies somewhere in default PHP or apache config. Or maybe permissions? I don't know... there is some LAMP vs C5 voodoo going on here.
Here is my Environment Info:
GET http://###/index.php/tools/required/files/edit?fID=24 500 (Internal Server Error) jquery.js:4
Where ### is my domain.
Eventually the image editor overlay loads, but just displays "Access Denied" in place of the editor.
PHP GD is present and enabled.
Similarly to tipweb, it works fine on my local LAMP stack under Mac OS 10.8.5, but not on my Digital Ocean stack.
I'm not using a php.ini file, so I'm guess the issue lies somewhere in default PHP or apache config. Or maybe permissions? I don't know... there is some LAMP vs C5 voodoo going on here.
Here is my Environment Info:
# concrete5 Version Core Version - 5.7.3 Version Installed - 5.7.3 Database Version - 20141219000000 # concrete5 Packages Album Box (0.9.3), Call to Action (0.9.1), Como Content (0.9.3), Floor Plans (1.0), Footer Content (0.9.3), Preferred Suppliers (1.0), Reserve Circle (0.9.3), Subscribe Circle (0.9.3), Xtreem Testimonials (1.0). # concrete5 Overrides blocks/autonav, blocks/testimonial, blocks/file, blocks/html, languages/sl_SI, languages/it_IT, languages/fr_FR, languages/nl_NL, languages/el_GR, languages/da_DK, languages/ru_RU, languages/tr_TR, languages/fi_FI, languages/sv_SE, languages/de_DE, languages/ja_JP, themes/como, themes/comohotel # concrete5 Cache Settings Block Cache - Off Overrides Cache - Off Full Page Caching - Off Full Page Cache Lifetime - Every 1 minutes. # Server Software Apache/2.4.7 (Ubuntu)
Viewing 15 lines of 44 lines. View entire code block.
Well, you should see the output of the query itself, click on the url and then look in the network pane (if you are using Chrome).
Hi Goutnet, Thanks for the response.
I pasted the console output in the first code block in my comments.
I did however figure out that it was a database issue, by trying to load the URL that was throwing an error in the browser:
http://###/index.php/tools/required/files/edit?fID=28...
(where ### is my domain)
The result was a Concrete5 error page with this:
(where ### is the name of my database)
This is because I migrated to a LAMP stack and I've had to manually rename all the database tables to use uppercase letters – very tedious and frustrating.
The issue is documented here:http://www.concrete5.org/documentation/how-tos/developers/mysql-dat...
And here is one of many threads around this topic:http://www.concrete5.org/community/forums/installation/table-names-...
I tried all suggestions in the documentation involving setting the lower_case_table_names config variable, but in the end I just had to rename all the database tables.
I pasted the console output in the first code block in my comments.
I did however figure out that it was a database issue, by trying to load the URL that was throwing an error in the browser:
http://###/index.php/tools/required/files/edit?fID=28...
(where ### is my domain)
The result was a Concrete5 error page with this:
An exception occurred while executing 'SELECT * FROM SystemImageEditorControlSets': SQLSTATE[42S02]: Base table or view not found: 1146 Table '###.SystemImageEditorControlSets' doesn't exist
(where ### is the name of my database)
This is because I migrated to a LAMP stack and I've had to manually rename all the database tables to use uppercase letters – very tedious and frustrating.
The issue is documented here:http://www.concrete5.org/documentation/how-tos/developers/mysql-dat...
And here is one of many threads around this topic:http://www.concrete5.org/community/forums/installation/table-names-...
I tried all suggestions in the documentation involving setting the lower_case_table_names config variable, but in the end I just had to rename all the database tables.