I am currently running Joomla 1.5, I have moved my site to a new domain and thought I had foloowed the procedure correctly. But now my menus are gone and it seems like articles are not showing up in their proper modules. Other than that the components i was using are now giving me a 404 component not found error. Does anyone know why this is or how I can fix this? Please I really need some help or direction....
Thanks
Here is my link: http://davidjamesmedia.ca
Make sure you check the following things:
Ensure you made the correct database setting changes in the configuration.php
Ensure you server is running PHP 5.2+
Make sure your MySQL version is arounf 5.0+ but also not too high such as 5.5.24 this can cause some problems with depreciated functions.
Also make sure your server has Apache mod_rewrite extension installed if you were using SEF before else you can turn SEF off in the configuration.php
Related
Try as I might, I can't get proper error messages in Joomla 3.1.5. No matter what I do, I get redirected to a nice "Error 0" page which doesn't tell me what happened where. I've tried setting error reporting to both maximum and developer in the admin console, and turning on developer mode. Is there any way to get proper error messages instead of friendly error messages to display in Joomla 3.1.5?
If you're not seeing the errors it's likely that you have an extension installed that is calling set_exception_handler(), while I don't have an STS 3.1 version anywhere to test the 3.2's we do have don't have any issues with reporting errors. (And as far back as I can remember, I don't believe Joomla core calls set_exception_handler().
We write Joomla extensions for clients as our primary business and I can tell you that the error reporting works. We have found in the past that some more dodgy extensions install their own exception handlers to hide issues in their code which is why we always develop and test on clear default Joomla installations.
Updated
Just saw your answer…
If that work's it means something is definitely calling set_exception_handler() which I don't believe is Joomla, I don't have have STS 3.1 installation but my current 1.5, 2.5 and 3.2's do not call set_exception_handler() in the Joomla core.
Few thoughts:
Check in Joomla the PHP information - see the error reporting local
value.
Check for a local php.ini file
Check if there is any ini_set code in your template...
Try adding a code like below, in your template's index.php file.
code:
<?php
ini_set('display_errors', 'on');
ini_set('error_reporting', E_ALL & ~E_NOTICE);
?>
Figured it out -- calling restore_exception_handler() gets rid of the poxy Joomla page and lets me read the text of the error.
Unfortunately today I got my Joomla 1.5 site hacked- the index.php has been overwritten and I've found as well a php script which does something nasty with the config.php file.
I've changed the FTP password, however since the config.php file contains as well the database user/password I'd like to change it as well. What is the right place to change it ? should I change it just in config.php or somewhere else ?
Changing the database password must be done via your hosting cPanel and then in the config.php.
Once you have done this, I would suggest upgrading to Joomla 2.5 as it is far more secure and has more features. You should also consider installing some security extensions. I answered a question regarding security which you can find in the link below:
Joomla! 2.5.4 Hacked: Having trouble with diagnosis
Here is also another bit of information I added regarding why keeping your Joomla version up to date is a good idea, if you don't already:
Why should I keep my Joomla version up to date?
Hope this helps
This is my first attempt at using Magento to develop a site. I have to admit the learning curve has been steep, but i have been able to navigate most of the challenges thus far. Here at the final hurdle, however, i have stumbled.
Specs:
Magento 1.7.0.2
Apache version 2.2.22
PHP version 5.3.10
MySQL version 5.1.65-cll
Magento is located in a folder on the server named magento one directory down, as in http://www.mydomain.co.za/magento
Problem:
No images are displayed in the front end or backend. It is as if it cannot access the stylesheets. When viewing the source, i can see that the paths are wrong. It searches for the stylesheets in http://www.mydomain.co.za/ and not in the magento folder. I can access the backend by typing in http://www.mydomain.co.za/magento/index.php/admin and that brings up the backend without any styling. After that however, every request results in 404. The URL looks like http://www.mydomain.co.za/magento/adminindex.php without a slash between admin and index. Introducing that slash manually after every 404 results in correct page being displayed (still without styling). So clearly the problem is here, but i can't seem to fix it. And YES, i do have the slash after the path in the database for both secure and unsecure.
Attempts to solve:
Changed the url’s in database link
Changed app/etc/local.xml to use correct database
Changed .htaccess to include this line: RewriteBase /magento/ (but i
removed it again)
Deleted the appropriate cache and sessions folders
Tried some of the suggestion given here link
Now, i am stuck. I have worked my way through error upon error (no fault of Magento, just the learning curve) and i am tired… :-( If someone can please give me some advice as to what to try next, it would be greatly appreciated.
I found these links of the (seemingly) similar problem. Clearly there is something happening here. The other thread never solved the issued, just found a work around. Is it possible that we have run into a bug? Something is stripping that slash out and it isn’t any of the usual suspects… dum dum dum
link
link
I'm a beginning Magento programmer. I used to access the backend as localhost/magento/admin and everything was working fine on WAMP. I could access any route I set up in config.xml as localhost/magento/(frontName) and my controllers were working fine.
Then I was trying to get Zend Debugger working with Eclipse, and in the process I fiddled with things, reinstalled WAMP and Magento a couple of times, installed Zend Server CE and later removed it, and MAYBE fiddled with some settings - don't remember exactly what I changed.
Ultimately, I'm back on WAMP, but now localhost/magento/admin is broken and the backend must be accessed as localhost/magento/index.php/admin, which is ugly. Also, I can't get any routes working. localhost/magento/(frontName) is broken, localhost/magento/index.php/(frontName) gives a 404 error within Magento.
I've been trying to fix this for nearly 2 days now; I'd be grateful for any help. Sorry about the n00b question.
And you are sure the mod rewrite is enabled? Can you get to the frontend at all? do you have sample data installed can you get to any products or categories?
you probably didn't understand very well how works exactly the config.xml in your controller. look at http://www.pierrefay.com/magento-create-controller-36
good luck
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!