Please make compatible with Concrete5.5
Permalink Browser Info Environment
I've been waiting for an add-on like this for a looong time! I tried to figure it out on my own but I just couldn't manage.
Do you think you can make it compatible with Concrete 5.5? Please, I really want to use this.
Do you think you can make it compatible with Concrete 5.5? Please, I really want to use this.
| Type: | Discussion |
|---|---|
| Status: | New |
sure, try 1.0.1
Thanks for acting fast...
I still get the following error
Maybe it's a problem with something on my website...
Thanks in advance...
I still get the following error
Warning: Cannot modify header information - headers already sent by (output started at /home/nikeb/public_html/packages/vanilla_forums/controller.php:28) in /home/nikeb/public_html/concrete/libraries/view.php on line 841
Maybe it's a problem with something on my website...
Thanks in advance...
thats a problem with your web server. you need to have permissions to move root/packages/vanilla_forum/controllers/login.php to root/controllers, and
root/packages/vanilla_forum/singe_pages/login.php to root/single_pages basically your server isn't letting you copy files tho.
then delete lines 20-57 in root/packages/vanilla_forums/controller.php
root/packages/vanilla_forum/singe_pages/login.php to root/single_pages basically your server isn't letting you copy files tho.
then delete lines 20-57 in root/packages/vanilla_forums/controller.php
Thank you very much... Not every developer takes the time to handle this tiny requests... =D
Be careful!! If you've already customized your login page and placed it into "root/site/single-pages/login.php" , the installation package will over-write your custom login page with it's own copy. I wish my server had stopped me from replacing my custom login page because now I have to re-customize it. At least the installation procedure could have backed up my file for me or warned me that it was about to wipe out all my hard work. Poor style points :-(
Other than that annoyance, it's a fine add-on and is working well for me.
Other than that annoyance, it's a fine add-on and is working well for me.
it actually has a check to make sure that that file doesn't exist already. Did that heck not work for you?
The first clue that it over-wrote the file was when I went to log in to my site and I was presented with your version of the login.php file. What is the installation program supposed to do if there is already a file there?
UPDATE: Yes I see the message: "You can't have the file login.php in root/single_pages. Delete it and try again" in your install function. I was not asked this question during the installation process.
The only reason to have a copy of login.php in the 'root/site/singe_pages' directory is to customize it so I think it's dangerous to tell users that they need to delete it in order to install your package. Perhaps it might be wise to inform them that they need to backup their customized file and apply the changes to your file. If I had known I needed to re-apply my changes, I might have held off installing the package until I had investigated things further. As it stands now, I have a botched up login page that I need to fix ASAP.
UPDATE: Yes I see the message: "You can't have the file login.php in root/single_pages. Delete it and try again" in your install function. I was not asked this question during the installation process.
The only reason to have a copy of login.php in the 'root/site/singe_pages' directory is to customize it so I think it's dangerous to tell users that they need to delete it in order to install your package. Perhaps it might be wise to inform them that they need to backup their customized file and apply the changes to your file. If I had known I needed to re-apply my changes, I might have held off installing the package until I had investigated things further. As it stands now, I have a botched up login page that I need to fix ASAP.
it was supposed to stop installation. Sorry, there was a bug for sites not in the root of their directories, and should be fixed in 1.0.2. sorry for the inconvenience.
Yes, my site is not in the root. I have edited my previous posts to reflect that fact. Thanks for looking into this so quickly.