Call to DB and Files outside the Public Folder |
Dear CodeIgniter Community, First post, Yay !
![]() Need some help. We are using Code-Igniter as the base frame for our website (custom tailored). The way it's programmed, we can call from the website to some files and databases that are stored outside the public folder (for security reasons), we had a domain/server transition few days back, and currently the website is broken because it's not allowing us to those calls (system_path). I'm wondering if you may point us in the right direction of what to double check or test. Thanks in advance ![]()
The main web works fine, http://mydomainname.com/
The error I get from all the child ulrs is this one: Quote: Internal Server Error I have tried the suggestions of the CodeIgniter troubleshoot page, because I am in doubt that my server is supporting the REQUEST_URI variable needed to serve search-engine friendly URLs, since I can actually see my own Index page but all the other URL's with CodeIgniter are printing the above error. On the config file I have: Quote:|-------------------------------------------------------------------------- And on the index file I have" Quote:/* As you can see, I changed
Is it something to do with the config in here ? : Quote:/* Also, what can I do to set or to add REQUEST_URI support on the server ? ![]() I hope I was able to explain myself ![]()
In general, if something doesn't work to fix the problem, you probably want to immediately change it back to its previous state before trying something else. I don't think the addition of the question mark in the config is especially helpful, as it really indicates that the configuration of the server is wrong (as the question mark should be part of the rewrite rule, if it is needed).
The first thing I would check would be to make sure that any .htaccess files and all configuration files were transferred properly to the new server. In some environments, it's relatively common for someone to use a tool to transfer files which doesn't include hidden files. Next, compare the web server's configuration to the configuration on the prior server. Also check the version of the web server, as you may need to make specific configuration changes when transitioning from one version to another (for example, Apache 2.2 to 2.4). Another consideration is the permissions on the files and directories. Whenever possible, I configure a group which includes the web server's account (usually apache or www-data) and the account(s) used to update/upload files and control permissions primarily based on group rather than owner, which reduces the likelihood that the server will be unable to access a file without requiring overly-broad permissions. A good read for understanding permissions is here: http://serverfault.com/questions/357108/...-webserver |
Welcome Guest, Not a member yet? Register Sign In |