CMS Made Simple Forums

This is basically the same issue as discussed in this thread, but since the blog post about 1.6.6 specifically mentions this issue as being addressed, I wanted to see if anyone's got any ideas.

The issue is that as an admin, someone edits a page and uses Tiny MCE to insert/edit image. When subsequently clicking the "Browse" icon, they are redirected to the login page, and so can never insert an image that has been uploaded through the image manager.

This issue has been going on from the start on this installation. The blog post on 1.6.6 mentions that it's caused by the host having session.use_cookies turned off. However, before upgrading to 1.6.6 I checked phpinfo() and it was indeed turned on. The subsequent upgrade to 1.6.6 didn't solve the issue.

This site is hosted by Network Solutions and the site seems to run slowly, but the client is reluctant to change hosts.

Relevant system info is below. Huge thanks to anyone who can finally address this.

Thanks,
Jon

CMS Version: 1.6.6

Installed Modules:
CMSMailer: 1.73.14
FileManager: 1.0.1
MenuManager: 1.6.2
ModuleManager: 1.3.1
News: 2.10.3
nuSOAP: 1.0.1
Printing: 1.0.4
Search: 1.6.1
ThemeManager: 1.1.1
TinyMCE: 2.5.5
Archiver: 0.2.1

Config Information:
php_memory_limit: 48M
process_whole_template: false
max_upload_size: 5000000
default_upload_permission: 664
assume_mod_rewrite: true
page_extension: /
internal_pretty_urls: false
use_hierarchy: true
debug: false
output_compression: false
use_smarty_php_tags: false
locale:
default_encoding: utf-8
admin_encoding: utf-8

PHP Information:
Current PHP Version (phpversion): 5.2.6 Success
md5 function (md5_function): On (True) Success
GD version (gd_version): 2 Success
tempnam function (tempnam_function): On (True) Success
Magic quotes in runtime (magic_quotes_runtime): Off (False) Success
PHP Effective Memory Limit (memory_limit): 48M Success
Maximum Execution Time (max_execution_time): 60 Success
PHP Safe Mode (safe_mode): Off (False) Success
Session Save Path (session_save_path): /tmp (1777) Success
Session Use Cookies (session.use_cookies): On (True) Success
Checking if the httpd process can create a file inside of a directory it created (create_dir_and_file): Success
PHP register_globals (register_globals): Off (False) Success
PHP output_buffering (output_buffering): 1 Success
disable_functions in PHP (disable_functions):  Success
PHP Open Basedir (open_basedir):  Success
Test for remote URL (test_remote_url):Success
fsockopen: Connection ok! Success
fopen: Connection ok! Success
File uploads (file_uploads): On (True) Success
Maximum Post Size (post_max_size): 10M Success
Maximum Upload Size (upload_max_filesize): 10M Success
Basic XML (expat) support (xml_function): On (True) Success
Test file_get_contents (file_get_contents): On (True) Success
Test ini_set (check_ini_set): On (True) Success

Server Information:
Server API (server_api): cgi-fcgi
Server Database (server_db_type): MySQL (mysql)
Server Database Version (server_db_version):5.0.75 Success
Server Software (server_software):Apache/2.2.8 (Unix) FrontPage/5.0.2.2635
Server Operating System (server_os):Linux 2.6.22.10-NETSOL On i686

Permission Information:
tmp, templates_c, modules, umask, all show 0775 Success
config_file: 0444 Success

I will test this issue in a bit....

The fixed issue in 1.6.6 was the iframing directly into ImageManager.... Could be that the iframe of TinyMCE to IM isnt done...

Ronny

Quick test on my box with session.use_cookies=0 doesnt show the login-screen...

Ronny

Ronny, thanks for looking into this.

Are you suggesting I turn off session.use_cookies?

Nope, I was just meaning that with the option set to off, I do get the correct imagepicker screen.... I have to try to get what drives you to the login-screen....

Ronny

Thanks, I can't tell you how much I appreciate your help. This has been driving clients crazy for months.

Let me know if I can give you any other info.

Jon,

do you have a link?

Ronny

Hi Jon,

I'm trying to reproduce your issue.
Can you please pm me a link to your site, containing a phpinfo.php file?

Thx. Rolf

Hi Jmires,

We have seen the problem on your site and we are trying to reproduce it. But no luck untill now...

Do you have access to the PHP error_log? If you do, are there any related errors in it?

Do you tried setting debug to true in the config.php and see if there are some point which might leed us to the course?


Grtz. Rolf

Hi Rolf,

Thanks for continuing to work on this. I checked PHP error logs - they're virtually empty. I sent you a PM with the one error log from the last month.

As for debug=true, this will generate debugging code on pages regardless of errors, right? I can't really put that on since this is a live site. Is there a way to only allow debug notices for a specified (my) IP address?

Thanks,
Jon

jmires

there isn't much to work with... 
Is it possible for you to make a second site on the same server where we can test?

www.test.website.com or www.website.com/test

®olf

Rolf wrote: Is it possible for you to make a second site on the same server where we can test?

Hi Rolf,

Good idea - I will set up a copy of the site where you can test. I'll let you know when it's up.

Thanks,
Jon

Rolf,

I copied the site and turned on debug. You can view/test/edit as much as you want at the subdomain dev (http://dev.domain.org).

The admin account you and Ronny were using should still work. Feel free to mess with anything you like on this, as for now you are the only ones using it.

Note that I can easily reproduce the problem with debugging turned off. With debugging turned on, it seems to show that the session is not found, so looks for cookies, finds no cookies, and so attempts to redirect to login page.

Many thanks once again. If you need me to turn debug off/on let me know. Right now it's on.

Cheers,
Jon

Hi,

Has this problem been solved?

BR

Graeme

Graeme,

Rolf and RonnyK are working on this. They have been looking at a site I've got so they can reproduce the problem, and they've seen it occur. I haven't heard anything new since my last post on Oct 12, where I copied the site to a subdomain so we could turn on debug mode and they could investigate further.

Thanks,
Jon