My Server's PHP has updated to version 5.3 recently. After this upgrade the drupal which is installed on my site doesn't load the pictures which are located in the '/sites/default/files/' directory. It throws 404 error for every picture stored in this path.
I am pretty confused with this. Do I have to make any change to my .htaccess file?
Is it possible directory permissions were changed when php was upgraded? That would be the simplest explanation, since I'm not aware of a reason why php 5.3 would itself cause this to happen.
I found that there was another .htaccess file in my 'sites/default/files/' folder. My web hosting company has obligated me to remove FollowSymLink. But I didn't know that there was another .htaccess file in my drupal folder. I removed that and now everything is working smoothly.
Related
I recently installed Laravel on my Ubuntu using composer, in the /var/www/html folder.
When i go to my directory however I am not served the Laravel welcome message, I just get Apache showing me all the files and folders in the directory.
My routes.php indicates that welcome.blade.php should be showed as default, i havent edited this, so im confused why it is not being served.
Please let me know what i might be doing wrong, if navigating to myip/myprojectdirectory
So I have this website, that some else build on Laravel. Since I need to make some changes I want to copy this website locally and make it work locally, so that later on I can apply the changes. I really don't want to work on the live site.
So I copied the whole website in my local folder but in order for me to see each page I have to follow this link:
http://localhost/XXXproject/html/index.php/auth/signin
I would like to know, where can I fix this. I want to remove the index.php from the url and be able to see the images without getting 500 errors everywhere. Something more like this:
http://localhost/XXXproject/html/auth/signin
And this is my htaccess.
RewriteCond %{REQUEST_URI} !^/html
RewriteRule ^(/?)(.*) /html/$2
During development I would recommend using Laravel's little HTTP server which will host the site without any external web server software such as Apache, where configuration might be an issue.
You can do this by going into the root directory of the project and typing:
php artisan serv
However if you do want to use a webserver for local development purposes with Laravel 4, you'll need to configure the rewrite rules appropriately. Although it does seem the rewriting is working to some extent, you may need to configure your webserver to consider index.php as a root document. Can't really help you more than that without more information on your webserver software and its current configuration.
Finally I solved it, I went through the installation and configuration steps from the website, and realize that I was working with a htaccess that was under wamp\www folder, I even tried making one for wamp\www\xxxproject.
But when following the steps I realized there is a htaccess inside the public folder from the project, I changed that one with the one from the website and now it works!
I'm using Joomla 2.5 and the backend is not shown correctly. It seems that the template is not loaded correctly.
This is my page:
http://www.fussball.tsg-kastel.de/administrator/
The page as such is shown correctly but as you see, the backend isn't...
Try doing this:
Rename the admin templates folder on the host server (for a backup)
FTP transfer of an admin template folder from another Joomla site and then copy it from the FTP location using a file manager into the admin templates folder.
You could have a corrupt file or just missing some files from installation. This has happened to people before and by doing these two steps it seemed to solve their issue.
Hope this works out for you.
You probably have a fatal error. Go to configuration.php and change error reporting to development. This will render the error to the browser (alternatively check your apache error log). I predict you probably have a plugin problem -- perhaps your host updated PHP version for example. Whatever it is, deal with that problem.
When I upload the CodeIgniter package to my web server on Bluehost, I can get into the main page, but not sure if this is all I have to do.
I've read many questions here about the same issue, but nothing worked for me. As I understand that I have to add some code .htaccess codeignitor code to the root .htaccess, but that made a mess in my url redirection.
I verified that mod_rewrite is working fine through some php code, but still unsure about the installation procedure. did any have this framework works on his Bluehost webserver??
I found the installation guide on this site, but the test fails back to 404 page.
By the way, I uploaded the package on a subdomain folder
Any comments are appreciated.
That's nothing wrong with Bluehost.. I've upload my CI into a subdomain folder in Bluehost. and nothing wrong.. It work perfectly..
Some questions :
Do you set your base_url correctly? or you can leave it blank.
Are you sure you've write the right .htaccess, and put it in the right place? make sure the index page in the config file is blank.
I am unfortunately getting a blank page when trying to run a site locally. There are other people running it locally just fine, so I am wondering if it could be something to do with my LAMP environment.
When I attempt to load the site, it's nothing but a blank page. I've ran php index.php in console and the error I get is the following "xajax Error: xajax failed to automatically identify your Request URI.Please set the Request URI explicitly when you instantiate the xajax object.". I'm not quite sure how to handle this in CodeIgniter and or at all to be honest.
I think it's a problem with LAMP configuration: check codeigniter folder permissions (add write permission to "logs" folder.
Thanks for your answer. I actually figured out what the problem was, it was like you said a problem with my LAMP configuration. Unfortunately XAMPP (which is what I am using and or was), the newest version uses PHP 5.3. Xajax doesn't support PHP 5.3 and this was causing the problems. After I went to an older version all was well!