Salam.
I have problem about codeIgniter. I using codeIgniter version 2.2.0, I create 2 projects with them. The problem is, when i open both projects at the same browser. and if i have login at project 1, and then i go to the project 2 (not have login at project 2) and doing refresh (F5) on project 2, then i coming back to project 1, the project 1 get logged out. why this happen?
Please help. what's wrong? Is that about my syntax, or about my codeIgniter version, or about my xampp version? I use xampp version 1.7.7. Thanks.
Its not your syntax nor browser or xampp version... When making new installations of CodeIgniter, there are certain variables that have the same name across installations by default... one of which is the sessions variable... So even if you have multiple installations of codeIgniter, by default, they would all be using the same session name which is why you are having that login or logout problem when you switch projects...
The solution now is to update the session name for each of your installations so they can be unique with no risk of corresponding with another installation...
Go to your application/config/config.php file and search for this line $config['sess_cookie_name'] = 'ci_session'; Change the value of each installation to something unique to your project e.g $config['sess_cookie_name'] = 'project1_session';
Thats all.
if you are using local host than use same system folder for all projects. If their is different version CI in your local host than it will create the issue.
I fix my issue with replacing system folder with the already exists in previous project.
You can check ci version by
echo CI_VERSION;
Related
I have a laravel project running on Linux server without any issue. The files are in /public_html directory and "laravel" directory is out of public_html. It has mySQL 5.6 and PHP 7.1. The project works completely fine.
Now, we have decided to move this on windows server. I have setup same PHP and mySQL on new windows server. I have double checked and this is correct.
I have imported entire database to windows and files have been moved as below:
The files from /home/abcuser/public_html/ directory to
C:\HostingSpace\abc.com\wwwroot
The files from /home/abcuser/laravel directory to
C:\HostingSpace\abc.com\laravel
The IIS has site path as below:
C:\HostingSpace\abc.com\wwwroot
I set all required permissions to these directories and updated database connection in .env file.
I am now getting blank page with no error message. Do I still need to make any changes in code? Did anyone has experienced the same?
Finally got this fixed..
I had to enable some PHP extensions. What I did is:
Checked the list of disabled PHP extensions from IIS of concerned
site.
Checked whether the particular extension is enabled in oldserver where
it is working.
And Enabled it as needed.
I tried to install Magento 2 on localhost using WAMP (php5.5, APACHE2.4.9 and MySQL5.6).
I added the required extension "intl" (by removing (;) in php.ini), but for some reason it didn't work - I had to copy the dll into the Apache bin folder.
I updated xdebug and had to create in php.ini an entry for xdebug.max_nesting_level = 50000;.
After all this I went to do the second phase of installation (database creation, etc...) and at the end it was successful. But upon trying to enter the Backend admin page, I get the error Page Not Found, and the Frontend was broken (no style).
So I installed the version with sample-date and the same thing happened, the only difference was the existence of the photos. I installed using the composer, and got the same error.
I think I did something wrong with the WAMP installation, but I'm not sure.
Another issue I encountered was on the themes in the installation with setup wizard: the app / design / frontend / magento folders are empty, while the github repository has two themes - why is that?
For broken styles and JS, please run php bin/magento setup:static-content:deploy. You might want to provide your specific language code as input; default is en_US
Re empty theme folder, there are several methods to deploy and install, based on your needs. The github version is meant for contributing devs, and hence there are themes present in the app/design/ folder. However, if you deployed via composer, or downloaded the zip file from magento.com, the app/design folder will be empty, since the themes are loaded via composer, from the vendor/magento folder.
I have downloaded latest version of magento from their website. When i am running it from browser like this localhost/magento it redirects me to www.localhost.com/magento. I am using windows 7 and wamp. All other projects on my localhost are working fine just magento is having this redirect problem.
This problem is occuring in office. I tried it at home on windows 8 using wamp it installed without any problem.
Do somebody know how can i solve this problem and run magento on localhost??? Please provide me some help
Thanks james for the responce. There is nothing related to database there because this was all happening before i set up the configuration. Any ways i updated my php version and downloaded the latest version and it is running without any problem. I was using 5.3.13 previously and i dont think that its that too old that magento start doing problem.
It sounds like the magento URL stored in the database is set to be www.localhost.com/magento when you want it to be http://localhost/magento
You can check this from a MySQL gui of the command line by running:
select * from core_config_data where path = 'web/unsecure/base_url';
How I work is by setting up in the VHOST for apache a serverName so magento.local, I then update my hosts file ( Sorry without doing a google search I dont know where this is located on windows ). Then use this URL in my magento database.
Either way check the SQL above's result compared to what you are expecting. If you have any more problems after this please paste the output from the SQL and I can help more.
I have a Joomla site running on a windows machine. The site was at 1.6 when some update requests came in. I decided to update the site, but the automated process didn't work, so I started FTPing the files up there manually.
I followed the instructions for the manual upgrade at http://docs.joomla.org/Upgrading_1.6.5_to_1.7 once I got the site to 1.6.5, but my problems had already started before that.
Now when I go to mysite.com/administrator most images are not there and when I try to log in I get kicked up to my site root rather than the /administrator folder. I took the opportunity to look at the code and none of the image src attributes or the form action attributes include "/administrator".
Soooo I need a little advice as to why this is happening. I would rather not have to restore from my backup and start over at 1.6. I was kinda hoping for this to be my first Joomla 3 site. Thanks in advance.
You said that you had trouble with updating Joomla via the admin panel, however did you check if the folders were writable? Site -> System Information -> Directory Permissions Always check this page once you have installed Joomla as it is the reason why a lot of people are unable to install updates or normal extensions.
You then mentioned that you had to upload the files manually via the FTP, however this is not requires. All that is required it to upload the update.zip to the foot of your Joomla site and unzip it.
As for a proper answer, May I suggest that you first update to the Latest version of the 1.6 series (1.6.6), then you download a fresh copy of Joomla 1.6.6, unzip the "administrator" folder, zip that folder, upload via the FTP to your Joomla root folder, then extract it. This will override all the default administrator files.
In the end I had this client move their Joomla install off Windows and onto a Linux machine. Things were just getting worse with the install and I threw in the towel. Thanks to Lodder for trying to help.
This can happen if you are using the JSecure plugin. It requires a token in the URL to enter the admin panel, for example:
http://www.yoursite.com/administrator?token
Explanation:
http://forum.joomla.org/viewtopic.php?p=2198164
I was able to fix this by removing the value that I had in the $live_site variable in the configuration.php file. I am also running this on a Windows server.
I did a cPanel move of a Joomla 1.5 website and a PHPBB3 forum from one server to another, and when the DNS changes kicked in all I see is a blank page. The administrator panel works without any problems whatsoever. cPanel works. Website and forum (which is separate from the website) are both blank.
I have then manually downloaded and then uploaded all files (didn't move the databases manually), and some files wouldn't upload because of 555 file permissions. I changed the permissions to 777 temporarily to overwrite the file with the manually uploaded one. So all files are now the same as they were on the old server.
Even when I turn the Site Debugging on, the screen is blank.
There is no hidden index.html or default.html file which could be causing the problem.
The entire account was moved with cPanel so it's the same on the old server and the new server. The hosting provider reports no problems. The DNS changes kicked in two days ago.
PHP is working, as this link works: http://oklade.net/findpath.php
In configuration.php, there is nothing specifically pointing to the old site.
var $dbtype = 'WeboMySql';
var $host = 'localhost';
All roads in these cases generally lead to configuration.php Check spelling and punctuation for mistakes. Also, enable one of the default Joomla Templates to be sure that whatever template you're using isn't also using old values.
Problem is solved.
The configuration.php file was to blame, as everyone suggested, but there was no possible way to change it manually and get it right, I had to make the system determine its own configuration.
I installed a fresh version of Joomla in a separate folder, and a fresh version of PHPBB3 in a separate folder.
Then I took the configuration.php and config.php files for those two things and put them in the existing folders of the website which didn't work.
Changed the minor details such as database prefixes (as I couldn't have entered the existing ones while installing), and that's it. Now it works.
So this might be a good workaround for anyone facing the same problem. Install a dummy version of Joomla and use the generated configuration.php file for the old, non-functioning website.
Before starting to debug the server, turn debug-mode on (in the admin CP)
First thing I would try is to delete the cache by running: rm –rf /var/www/html/<your website directory>/var/cache/*
The next thing I would try is to switch to another template - make sure that the template is not the issue.
Also, make sure to check the apache access log - just in case. also, you can check .htaccess for stuff like 301 redirect rules or any other problematic configuration (same applies for httpd.conf and configuration.php)
Good luck!