Issues in concrete5 on IIS
Permalink
Hi everyone,
I have built concrete5 by WebMatrix(Web Application Gallery).
Install is OK. But, for some settings can not be, I have stopped.
1.Theme activation
URL of the concrete when activate the Theme is contain a colon. The colon is a reserved word has a special meaning on Windows. Therefore, if this is contained, an error may occur. Please see below forum thread.
http://social.msdn.microsoft.com/Forums/en-US/wspsupport/thread/d8d...
2.Addons update
In concrete installed by WebMatrix (Web Application Gallery), update of addons will generate the next error.
Unable to backup old package directory to 'c:\[absolute path]/files/trash'
I think the value of DIR_FILES_TRASH is strange.　This is a issue reproduced even if you try.
I have still not been able to solve this issue... Someone please help me.
I have built concrete5 by WebMatrix(Web Application Gallery).
Install is OK. But, for some settings can not be, I have stopped.
1.Theme activation
URL of the concrete when activate the Theme is contain a colon. The colon is a reserved word has a special meaning on Windows. Therefore, if this is contained, an error may occur. Please see below forum thread.
http://social.msdn.microsoft.com/Forums/en-US/wspsupport/thread/d8d...
2.Addons update
In concrete installed by WebMatrix (Web Application Gallery), update of addons will generate the next error.
Unable to backup old package directory to 'c:\[absolute path]/files/trash'
I think the value of DIR_FILES_TRASH is strange.　This is a issue reproduced even if you try.
I have still not been able to solve this issue... Someone please help me.
Does anybody know this issue and solution?
Hi limone919,
I think the lack of replies may be because of your choice of platform to run Concrete5 on.
Although Concrete5 may be able work on IIS, it isn't a platform that is recommended. Because of that, most people don't run it on IIS, and therefore there isn't as many people that might recognise these issues.
According to the System Requirements page on this site, IIS isn't part of the testing process either. So you may run into undiscovered bugs like the ones you have come across, simply because Concrete5 is designed and tested for a LAMP stack (and I'd safely say MAMP as well).
Someone may still be able to help you, but I'd suggest you might be better of shifting your site to a different host, as you don't know what other problems you might encounter.
I think the lack of replies may be because of your choice of platform to run Concrete5 on.
Although Concrete5 may be able work on IIS, it isn't a platform that is recommended. Because of that, most people don't run it on IIS, and therefore there isn't as many people that might recognise these issues.
According to the System Requirements page on this site, IIS isn't part of the testing process either. So you may run into undiscovered bugs like the ones you have come across, simply because Concrete5 is designed and tested for a LAMP stack (and I'd safely say MAMP as well).
Someone may still be able to help you, but I'd suggest you might be better of shifting your site to a different host, as you don't know what other problems you might encounter.
mesuva,
Thank you for your reply! I understood your remark well.
Surely, there is almost no user who is using concrete5 on IIS. But a bug and it are another problems.
Since it corresponded to web platform installer, an IIS user also increases rightly from now on.
For example, WordPress is fully compatible with both of the Apache / IIS.I think it impossible to carry out full compatible suddenly. Therefore, I want to erase a bug little by little.
A small hint also welcomes. Please advice me..
Thank you for your reply! I understood your remark well.
Surely, there is almost no user who is using concrete5 on IIS. But a bug and it are another problems.
Since it corresponded to web platform installer, an IIS user also increases rightly from now on.
For example, WordPress is fully compatible with both of the Apache / IIS.I think it impossible to carry out full compatible suddenly. Therefore, I want to erase a bug little by little.
A small hint also welcomes. Please advice me..
I think that it is a problem that the absolute path and the relative path are intermingled. But I can't understand. Which file should be edited in order to correct this.
Anyone? plz help me.
Isn't there any mind which crushes bugs? If so, concrete5 is not suitable to participate in the WAG.
Hi limone919,
I do not have the experience to help you with your specific problem... but if you truly feel it is a bug, the proper place to report it ishttp://www.concrete5.org/developers/bugs/5-4-2-2/...
where it may be examined more closely, rather than on the forum as apparently no one else has experienced your problem and solved it yet.
I do not have the experience to help you with your specific problem... but if you truly feel it is a bug, the proper place to report it ishttp://www.concrete5.org/developers/bugs/5-4-2-2/...
where it may be examined more closely, rather than on the forum as apparently no one else has experienced your problem and solved it yet.
This is just a guess, but in config/concrete/app.php and config/concrete/site.php, have you tried changing the '\' to a '/'?
I mean, '/' to '\'
