magento sites are broken after updating phpMyAdmin - php

I need help to resolve my problem.
Suddenly my magento sites are broken, all pages, not only front pages but also backend pages, redirect install page, http://hogehoge.com/index.php/install/.
I don't know why this kind of problem happen.
Of course I checked server logs, my server is attacked or not but I cannot find attacked logs.
But I find one supposed reason, I think after updating phpMyAdmin my magento sites are broken.
On my server, not only magento but also another application, wordpress, piwik and so on, work but only magento had problem.
If all applications were broken, I could understand, but only magento broken I want to know what wrong is.
Maybe if I can repair by magento-db-repair tool, it's ok but I think I can't make solution basically.
So please advise me what I should check my server configuration.
My server spec is
Centos6.4 64bit
apache2.2.15
php5.4.23
mysql5.5.35
phpMyAdmin4.1.1(<=update from 4.1.0)
magento1.7.0.2 and 1.8.1.0
Thank you.

Related

Google undetermined malware fix for WordPress

Just today when I tried to access my site I got a warning saying my site has harmful content.
I have tried scanning the site with clamAV and some other online sites for virus scan but did not find anything. I submitted my site to Google and it is still saying it is malicious. There is no sample URL for the malware, it only says "Undetermined malware"
I am using WordPress, there was no plugin updated recently. How can I find which part of my site is infected?
I tried console of google chrome, tried installing new anti-malware plugin (nothing found), tried to scan the site with different other websites and such but nothing gave any positive result.
Security on a website is very different from security on a home computer. Fixing this will be hard for someone who knows what they are doing, you have a lot of learning to do ahead of you before you will be able to accomplish this effectively. As a first step you need to try to identify when the problem started and revert to an earlier backup. Then remove ALL plugins, upgrade your WordPress installation to the latest version then change all the passwords associated with your site, then ONLY install the absolutely essential plugins - and make sure its the latest production versions of these.
This might fix the problem.

Fresh Wordpress install not reflecting changes on files instantly

I have a fresh wordpress 4.0 install on my server for a specific domain and when I make changes to any of the theme files it won't show up in the browser for a few reloads. I just add "asdf" to the theme file to test changes. I can refresh 20 times but no changes show up until like 20 seconds later.
What I have tried:
Turned off firefox's cache.
Turned off wordpress cache.
Tested other domains on my server with wordpress and they work properly.
Installed wordpress with "server installer apps"(3 times) and also with manual installation.
I refresh with ctrl+f5
Tried with firefox and with chrome, same results.
Its a fresh install so no plugins, no settings changes. There is no caching and my other domains work properly. No errors show up in the console.
I have no idea what the problem could be. My server company, mediatemple, said it could be my ISP, but other domains on my site work properly from the same computer/network. For some reason the problem is specific to this domain and the problem persists through all the themes.
I don't know what to do next. Any suggestions would be greatly appreciated. :)
Update:
Have tried manual install of wordpress 3.9 and that does nothing.
I added a new folder to the root and in that folder I added a file called index.html to test if this file, which is unaffected by wordpress, would show instant changes and IT DOES. So the problem seems to be based within wordpress and specific to this domain.
I spoke to Mediatemple for the 3rd time now and this guy was much more helpful and he actually solved the problem.
When you add a domain to mediatemple it automatically sets the PHP version to "FastCGI", which normally is fine, but it caused problems specifically on this one domain's wordpress install for unknown reasons. So he switched the PHP version to "CGI (Stable)" and that fixed every problem.
I hope this will be helpful to someone in the future. :]

Wordpress plugins are active but not checked in admin tool

Ok, so I have a big problem. Or at least an indication of a big problem. You see I went to create a dev version of a recently launched site. I copied all the files over to a new directory, created my apache entries, created a brand new database for it, and copied over that database.
Then I made sure to change the www.mysite.com entries to dev.mysite.com in the database. All of that looked good and I restarted apache. After running into some issues with the dev site I decided to back away for the night. I went to check the production site and it was suddenly down. So I removed the SSL entry in default-ssl in Apache and restarted Apache again and that was fine.
Then I went into admin and noticed that on the plugin page it bolds the active plugins. It gives an accurate count. And the plugins are working. But the checkbox next to each isn't showing checked.
So I thought that maybe I messed up the database on accident. So I just blew away the db and re-imported it really quick from the backup I made before all this started (about 30 minutes ago). And it looks the same. The site is working, but I am having problems with admin.
Does anyone have any advice? This is freaking me out a bit. I have never had a problem like this before with creating a dev site and never had Wordpress do crazy stuff like this before.
I will add that this is running the latest version of Wordpress and WooCommerce. It seems like the site is working. But this is leaving me very concerned about other issues.
The checkbox next to my active plugins isn't checked either. I think this is normal. You check them yourself in order to apply bulk actions to multiple plugins at once (e.g. check three plugins and then use the bulk action dropdown to active all three at once).
Sorry if I've misunderstood your problem here.

Cannot load /admin after migrating SilverStripe install to a new server

I have just moved a silverstripe install to a new joyent smartos server. Not being familiar with Linux, this was still relatively easy.
I am new to silverstripe as well, but the team here has developed on it for years.
I have the site up and running on the new server, but have not pointed the domain to it until we can thoroughly test it. So I am accessing it from it's ip address. The site displays fine and the sub pages work as well. When I navigate to the '/admin' page, I see a silverstripe page that states the page cannot be found (not an Apache 404). I copied over the .htaccess and the _config.php from the old server, so there should be no issues.
I have done a /dev/build with no errors and I can log in through the security page, but I just cannot get the /admin to come up. I am lost after spending the whole morning surfing google to find the answer. Any help would be greatly appreciated.
UPDATE:: I installed a fresh version of silverstripe into a subdirectory on the same server. Works perfectly, so that rules out any PHP issues.
I have also tried /index.php/admin with no luck.
Thanks,
Ben
I was having this problem as well. None of the solutions I found online worked for me, but I managed to figure it out.
I had apache running as a non-standard user, and the problem turned out to be that the webserver was unable to save session data for the logins.
The solution in my case was to chown root.myuser /var/lib/php/session. Once done, the admin page loaded fine.
If /admin is not loading at all and there is no 404 error, there is a high chance of a PHP error. And that should be logged in the webserver's log file. This will depend on your operating system and probably on the Joyent environment (not familiar with that breed of cloud computing). On Debian, Ubuntu, and some more it's /var/log/apache2/error.log (assuming you're using Apache).
If I had to guess, I'd say the permissions of assets/_combinedfiles/ are bad. The webserver tries to create some combined JS and CSS files there (specifically leftandmain.js and cmsmain.js) and if it fails, you might get the dreaded white page of death in /admin.

Magento module works well on localhost but not on live server

I have a weird case here....
I'm making a simple magento module right now. Some kind of script injection module (similar to google analytics module). I've built the admin config for that module (which is defined from system.xml)
as seen on the image. This module works very well on my localhost. But it's getting weird on the live server. The modules looks like it doesn't enabled at all although I have totally make sure it's all already enabled. Both via magento admin area and also via app/etc/modules. That admin config area never appear on live server's magento installation.
does anybody know what's the issue with this problem?
or at least tell me how and where should I debug it? I've been digging it to magento core code but getting stuck on getSingleton() function somewhere around magento core code. I don't understand that way-too-MVC stuff :p
I would be very glad if someone could explain and guide me on this
thanks :)
The most common problems are associated with case sensitivity. If you have Windows hosting, then the error in the uppercase/lowercase characters is not visible and it works. But as soon as it gets to linux hosting, the module will not work.
Check the paths in the settings and folders/files - so that they match.
Usually there are three things:
typos in xml files (validate them with validator)
cache is not cleared after installation (clear cache)
ACL rules are not reinitiated (re-save admin roles)
If you adjust the layout/add your own layout in the backoffice of magento, it's best to clear the cache (remove everything in the var/cache/ folder) and to logout and re-login.
Thumb rules while deploying magento custom module on the live server-
Deploy your custom module
Flush your all magento cache or at-least refresh them
[System->Cache Management]
If you have enabled compilation re-run the compilation or disable compilation until the testing is done.
[System-Tools->Compilation]

Categories