Need to change the database password for my Joomla site - joomla

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

Related

Joomla Site is hacked?

My joomla site is hacked by someone.The hacker change the content of my files and replace their content. I find it and deleted but again and again he is doing this.I changed my ftp and cpanel details.But no use.How to prevent this.Please help me any one
Thanks In Advance
For the moment, at least update to 1.5.26 and after that also install this patch.
Remove any unneeded extensions and also try to make sure that the rest of your extensions are up-to-date as much as possible.
You can also strengthen up your site's security with advanced .htaccess rules and security extensions like admin tools by Akeeba.
Read also:
Joomla Security Checklist
https://joomla.stackexchange.com/questions/2305/what-to-do-if-my-joomla-website-got-hacked
Also, this Google Search Results Page will present you with links to useful and important information.

Magento Admin URL 404

I know that that similar issues and topics exist, however my issue differs slightly and none of the proposed fixes have worked.
I was accessing the Magento backend as normal. Approximately 10 minutes after that I could no longer access the Magento backend.
What I mean is that when I go to the admin url login page, I get a 404. However the 404 isn't generated by my host, it's generated by my webstore.
Everything about my webstore works as normal.
I've seen a number of fixes, mainly this one...
http://www.magentocommerce.com/boards/viewthread/207981/#t274443
I have a few main issues.
Admin Custom URL had been set (but not by me). It was set over a year ago when Magento was installed. It worked entirely fine until today.
I do not even have "admin/url/custom" and "admin/url/use_custom" in my "core_config_data" PHP table. It simply does not exist so I cannot change it. I looked manually for it and did a search for it. Nothing.
I tried updating the local.xml file and clearing "var/caches" and "var/sessions" but that did not work either.
I've been working this for hours and it's beyond frustrating. It's imperative that this be fixed ASAP because we are a fairly sizeable company.
Thanks ahead for helping. Anything at all would be appreciated.
First Check your Apache configurations
I know that you said you were only in the Magento admin but I would first check that apache was configured correctly. This is the first point of contact and you need to ensure that it's working right.
You need to locate a default Magento htaccess file that you can upload to your server. There's additional configurations that you need to make if you're in a subdirectory and also check to make sure that your mod_rewrite is working properly. There's an extensive tutorial on these things here, magento htaccess.
Make sure that you have the right magento admin url
I have to assume that you know what your magento admin url is, but of course I would double check that you're getting it right. There is an option in the admin area to change the admin url, you could have adjusted that on accident.
You say that you don't have "admin/url/custom" and "admin/url/use_custom" in your core_config_data table. This actually means that you didn't set the magento admin url from the admin area. However there is a third place that you can look for your admin url. This is in app/etc/local.xml but you couldn't have changed this from the administration area.
Did you turn off search engine friendly urls?
If you had been accessing your administrative area using /admin and then accidentally turned off SEF urls, then your admin area could have just simply moved to /index.php/admin. Of course you mentioned that you have a custom admin url, but I don't know what that is, so I'm giving examples with the default.
I can't really give you any more suggestions without more information. I hope that this helps!
Found this and thought I would post here since it shows up in google.
http://sourcelibrary.org/2011/05/19/magento-404-page-not-found-error-for-admin-panel-access/#comment-8444

Joomla front end has no content after web server move

I am so stumped with this and I need some help from the community. I moved my joomla site over to a new server and now the content has disappeared from the front end, I am not getting an errors.... Can someone offer any suggestions on where to look for the problem? my config is fine and I am pretty sure my database is aswell because all my original articles are there.
I am running Joomla 1.5
The URL: http://www.davidjamesmedia.ca
If you moved to a new server at a different hosting company, Joomla is probably either
not looking in the right place for the database, or
not using the right credentials (host, port, username, password, whatever) for the database.
That might also be true if you moved to a different server at the same hosting company, although it's a little less likely. Look at the configuration.php file.
Assuming you have shell access, make sure you can access the database through its command-line utility. Then make sure Joomla is using the same credentials.
This is a really odd one.
The database credentials are obviously correct otherwise the site wouldn't load at all and would result in a MySQL error. Try re-assigning a new temporary article to the homepage else download the K2 component, import your articles and assign the K2 article to the homepage.
Update:
If you have the demo package for the template you are using the follow these steps:
create a sub domain
install the demo package with sample data
export the #__content database table from the main website
replace the #__content table with the one you exported
Make sure your error reporting is on in your server's php.ini file so that you can see what errors php is giving i.e. error_reporting = E_ALL & ~E_DEPRECATED
In admin panel, can you see the articles in content menu?
If so, enter in each article and push the Save button.
After you save the article, it should appear again in frontpage (that worked for me).

Joomla - Component 404 and blank front Page

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

Moved Joomla 1.7 Site to New Server. Admin works fine. No pages display

I've just moved a Joomla 1.7 site to a new server.
Administration back-end works fine. Configuration.php seems fine. Get "The requested document was not found on this server." for every page other than Home.
Must be talking to the database OK or I'd get an error. Could this be a problem with the PHP?
Thanks,
Andy
Did you clear joomla cache ?
Disable page and/or module caching.
Disable any plugin that optimizes "loading speed".
Try removing SEF URLs (Joomla! and any 3rd party extension).
If you are using a custom .htacess, then use an unmodified joomla one.
Disable some system plugins.
Disable modules in the homepage.
Have you tried using another template (site) ?
You have Seach Engine Friendly URLs enabled in /administrator/ area's global configuration settings. You have probably enabled the option to use the mod_rewrite function which removes the /index.php/ portion of the urls.
It is a requirement of this mode that you have the .htaccess file in place in the root of your site. You probably had this correctly configured on your development server but perhaps forgot to move the file across when you went live. Some FTP programs hide dot files (files starting with a leading dot in the filename) so depending upon how you transferred the files (I'm guessing manually with FTP rather than Akeeba backup or similar) the file may have been missed. Look through your FTP client's options/preferences for an option to show/hide hidden files.
Failing this - the file could be correctly in place - but if you were developing in a sub-folder on your development server you would have set the RewriteBase line to your /sub-folder/
RewriteBase /sub-folder/
Now you've moved to the live server this line could be incorrect. If this is the case, edit the file to Read
RewriteBase /
Chances are it is one or other of these issues - missing .htaccess file or incorrect RewriteBase. A third and nowadays somewhat more unlikely option is that your server doesn't have mod_rewrite enabled - but I think that would result in server 500 errors.
Check whether you are using any modules that is calling database and you have not changed DB details in that module after migration. If admin panel is working fine then I think problem with some modules that are used in front-end. You can do debugging by disabling few suspected modules and check whether your site works fine or not. Else provide some more information about your site so that I can check further.

Resources