Solution:

1. Either you upgraded the lastest phpmyadmin 3.4.10.x.
2. They provide the patch file. If you cannot find it then simply change the code in the given file as follows:
Old:
$this->getBacktrace()

New:
serialize($this->getBacktrace())

Hope this helps someone having the problem.

The installation and configurations of PHP, Apache and MySQL in Windows has also become quite easier these days because they provide some default configurations. As PHP, after its latest releases i.e.5.4, does not provide the downloads of VC6 version (the PHP compiled with Visual C++ 2006 compiler) these days because it is believed that the performance of the PHP compiled with VC9 (compiled with Visual C++ 2008 or later) has improved quite a lot than the compiled with VC6. So to work with the latest VC9 version of PHP, you must have installed PHP with VC9 compiled Apache as well or you use IIS as web server. VC9 compiled Apache is provided by Apache Lounge (apachelounge.com) not the original Apache (apache.org). Since I haven’t worked yet with IIS and always work with Apache in anyway, I don’t have knowledge about the IIS & PHP. Here I am going to explain few steps on how to install PHP 5.4 and Apache 2.4 in Windows.

Requirement

To run the applications compiled with VC8 or VC10, it is required to install the respective (or latest one is always better) Visual C++ redistributable packages. You can download the package from Microsoft’s official site for free.

• To download Visual C++ 2008 – http://www.microsoft.com/download/en/details.aspx?id=5582
• To download Visual C++ 2010 – http://www.microsoft.com/download/en/details.aspx?id=8328

Note: If you have any Visual Studio installed in your PC then you don’t have to install them separately.

Where to install?

Since I have not used any installers for both PHP and Apache, I will be downloading the pre compiled zipped packages and install them in my D drive. The folder structure will look like below:

• d:/etc/apache                                   – Apache installation
• d:/etc/php                                          – PHP installation
• d:/etc/mysql                                      – MySQL installation
• d:/etc/mysql/databases               – MySQL data folder
• d:/etc/www                                       – document root folder

Note: You can change the drive and path for the installations in your own way.

Download

1. Download the latest Apache 2.4.1 (as of writing this) from http://www.apachelounge.com/download/ (direct link for the current version – http://www.apachelounge.com/download/win32/bins/httpd-2.4.1-win32.zip) and unzip it in d:/etc/apache
2. Download latest version 5.4 from http://windows.php.net/download and unzip it in d:/etc/php. While downloading PHP, choose the Thread Safe version for windows.
3. Download the PHP and Apache connector DLL file from http://www.apachelounge.com/download/ (direct link: http://www.apachelounge.com/download/win32/mods-2.4/php5apache2_4.dll-php-5.4-win32.zip) and extract the file php5apache2_4.dll and copy it to d:/etc/php.

Configurations

Though the configurations may vary from individual’s requirement but here I will be discussing for some basic configurations in PHP and Apache.

Apache

1. Open the file d:/etc/apache/conf/httpd.conf in any text editor (I use my lovely Notepad++) then find and make the following changes/configurations as per your installation path.
2. Set the server root

   ServerRoot "D:/etc/apache"

3. Enable required Apache modules. I just uncomment one more for mod_rewrite module.
4. Add the following lines somewhere (I did just below the module enabling)

   LoadModule php5_module "d:/etc/php/php5apache2_4.dll"
   AddHandler application/x-httpd-php .php
   PHPIniDir "d:/etc/php"

5. Change server admin email address

   ServerAdmin info@yoursite.com

6. Change the document root:

   DocumentRoot "d:/etc/www"
   <Directory "d:/etc/www">

7. If you want to allow .htaccess to be used under document root do the following under <Directory “d:/etc/www”>

   AllowOverride All

8. Find the follwoing and replace the path:

   ScriptAlias /cgi-bin/ "d:/etc/apache/cgi-bin/"
   <Directory "d:/etc/apache/cgi-bin">

9. Add index.php in directory index

   DirectoryIndex index.html index.php

PHP

1. Rename php.ini-development to php.ini
2. Find extension directory setting and set the path as per your installation.

   extension_dir = "d:\etc\php\ext"

3. Uncomment (remove the simicolon ; from the beginning of the line) the extensions that you want to enable them. i.e.

   extension=php_curl.dll
   extension=php_mysql.dll
   extension=php_mysqli.dll
   extension=php_pdo_mysql.dll
   extension=php_soap.dll

4. If you want to test email sending from the PHP in local system, then you need to set the SMTP. i.e.

   SMTP = smtp.yoursite.com
   smtp_port = 25
   sendmail_from = youremail@sender.com

Rest of the changes/configurations are totally depends on requirement project wise.

Set Environment Variables for PHP (Windows 7)

To be available PHP globally in Windows, the path of the PHP has to be set.

1. Right click on Computer and click Properties
2. Click on Advanced system settings on the left side (top).
3. Click on the Environment variables
4. Under System variables, double click the Path variable name and add ;d:\etc\php without double quotes at the end where semicolon (;) is the separator.
5. Click OK to save. Sometimes you may need to restart the computer this to take it into effect.

Install Apache as Service

Since we have just copied the files in a folder, the Apache is not yet not a windows service. To install it as a service follow the steps.

1. Run the command line (cmd.exe) As Administrator. Browse the folder c:\Windows\System32\ and right click on cmd.exe and select Run as Administrator.
2. Change directory to d:\etc\apache\binin the command line

   cd d:\etc\apache\bin

3. Run the command to install it

   httpd -k install (or sometimes httpd.exe -k install if that does not work)

Now restart the computer and test both PHP and Apache. To test both together create a PHP file phpinfo.php in d:\etc\www. Now browse in the browser as http://localhost/phpinfo.php.

If you can see the PHP information then now you are done !

Steps:
I did the following steps to upgrade Magento 1.4.2.0 to 1.6.1.0:

• - Installed fresh 1.6 Magento with fresh sample data (sample data should also be the latest 1.6 version).
• - Re-indexed all the items from back end of installed latest Magento 1.6.
• - Disabled all the cache from Magento back end.
• - Flushed/deleted all the Magento cache.

  rm -rf var/cache/* var/session/*
  rm -rf downloader/pearlib/cache/* downloader/pearlib/download/*
  

• - Prevent unique check while upgrading by changing file app/etc/config.xml

  SET NAMES utf8;

  To

  SET NAMES utf8; SET FOREIGN_KEY_CHECKS=0; SET UNIQUE_CHECKS=0;

• - To trace the errors, I renamed the errors/local.xml.sample to errors/local.xml.
• - Edited the app/etc/local.xml to connect to the old database.
• - I was working in Ubuntu, so in terminal, I ran the following command in the Magento 1.6 installed root directory.
  php index.php
  (If in case of windows just hit the Magento home URL in the browser and wait till it ends)

The above steps are standard steps for all of the Magento upgrades. But troubleshooting may vary depending upon the Magento system, version, extensions used, data, extra attributes added, etc.

Troubleshooting while upgrading:
Problem:
First of all I encountered the error of it failed renaming the core_url_rewrite table. I don’t know why does it really needed to rename it but the error was on renaming it. I tried several times but I always found the same error with “core_url_rewrite” table. I was almost stopped here. There was nothing except pulling the hair out even after a many times of googling.

The error was with that table and I tried by trunctating the table but no luck. Next I tried by dropping the table but again no luck.

Solution:
I droped the table from old table and imported the structure of the table from new 1.6.1.0 database and tried to upgrade again then it worked for me. You do not have to worry about the data in this table because while reindexing, the data will be filled out again.

Problem:
Secondly, there was an error for customer integrity constraint violation.

Solution:
I compared the structure of customer_entity (of new and old database) and found “website_id and email” should be unique in new structure. Checked if there are duplicate entry with those two fields:

SELECT *
FROM `customer_entity`
GROUP BY website_id,email HAVING COUNT(entity_id)>1

Found one email address was duplicate for the same website and I deleted one.

Then again ran the command :

php index.php

It took around 1 hour but this time there was no message. That means my upgrade has been done

Then flushed the cache again!

Change the base URLs in the “core_config_data” table for the path “web/secure/base_url” and “web/unsecure/base_url”.

Reindexing:
Before visiting the site, don’t forget to reindex.

php shell/indexer.php --reindexall

Again flushed the cache.

rm -rf var/cache/* var/session/*
rm -rf downloader/pearlib/cache/* downloader/pearlib/download/*

Then I visited the admin site. I was able to login to the admin with new version of Magento.

I did not stop here. Not to take long breath yet. Now I had to check each and every menus available in Magento back end. All were working fine but product edit page was with fatal error and order detail view page was with broken design but no error found.

After some research and study about modules used in the old database, extra attributes used in old version, I thought I had to delete all the attributes and module related data.

I tried my best to search the modules related data and attributes in the database and remove them. I had removed some attributes, I had updated some attributes which has used models from “eav_attribute” table. And I had to remove the modules setup data from “core_resource” table.

Search:

SELECT * FROM `eav_attribute` WHERE `attribute_code` like 'aw_%';
SELECT * FROM `eav_attribute` WHERE `attribute_code` like 'bcp_%';

Set all the models that attribute calls to NULL and remove the attribute from being System Attribute (`is_user_defined`=1) so that it can be removed from the admin Attribute Manager.

UPDATE `eav_attribute` SET
`attribute_model`=NULL,
`backend_model`=NULL,
`frontend_model`=NULL,
`source_model`=NULL,
`is_user_defined`=1
WHERE `attribute_code` like 'aw_%';

For another extension:

UPDATE `eav_attribute` SET
`attribute_model`=NULL,
`backend_model`=NULL,
`frontend_model`=NULL,
`source_model`=NULL,
`is_user_defined`=1
WHERE `attribute_code` like 'bcp_%';

I also removed those extensions entry from “core_resource” table.

DELETE FROM `core_resource` WHERE `code` = 'awall_setup'
DELETE FROM `core_resource` WHERE `core_resource`.`code` = 'bcp_setup'

Do not forget to flush the cache again before running the site.

rm -rf var/cache/* var/session/*
rm -rf downloader/pearlib/cache/* downloader/pearlib/download/*

So in my case, specially the AW extensions and their attributes were the cause of the error in product listing and order view page.

Hope these steps will help the people who are really desparate to upgrade Magento systems and having trouble. I believe at least some of the steps and troubleshooting tips will help someone.

Enjoy!!

I migrated successfully a Magento shop from 1.4.2 to latest version 1.6.0. I was trying to move my local files to my Ubuntu system. While migrating I was using a different sub domain and now I am trying some different tasks with different sub domain. I just made a copy of the running site (files and DB) and made requried configurations. And tried to login to the admin with correct username and password, I was just redirected to the same login page without any errors/warnings/messages. When I entere wrong username/password then it shows me the error.

That was quite annoying .

I looked in the google and found one solution to modify (comment some lines of code) in the core file (app/code/core/Mage/Core/Model/Session/Abstract/Varien.php) as follows:

$this->getCookie()->getPath()//,
 // set session cookie params
 session_set_cookie_params(
 $this->getCookie()->getLifetime(),
 $this->getCookie()->getPath()//,
 //$this->getCookie()->getDomain(),
 //$this->getCookie()->isSecure(),
 //$this->getCookie()->getHttponly()
 );

It was written that for 1.4 it has to be something like below:

/* if (!$cookieParams['httponly']) {
   unset($cookieParams['httponly']);
   if (!$cookieParams['secure']) {
     unset($cookieParams['secure']);
     if (!$cookieParams['domain']) {
       unset($cookieParams['domain']);
     }
   }
 }
 if (isset($cookieParams['domain'])) {
   $cookieParams['domain'] = $cookie->getDomain();
 } */

When I comment these lines and tried and it worked. Strange!!!

Then I dig into the Magento core files and tried to find what exactly these lines of code check and found that they check the domain for the cookie stored in the core_config_data table. I saw a row in core_config_data table having the old sub domain with the path ‘web/cookie/cookie_domain’. Then I changed this domain value to my new sub domain and uncomment above lines of code.

Then it worked!! Bravo!!!

Magento always rocks but before rocking it sucks for a while…

Good luck others!!!

Joomla 1.0

In Joomla! 1.0.x it was possible to determine if the user was viewing the front page by using code like this:

if ($option == 'com_frontpage' || $option == '') {
	echo 'This is the front page';
}

Joomla 1.5

But in Joomla! 1.5.x the com_frontpage component is no longer present. This is how to achieve the same result in Joomla! 1.5.x

$menu = & JSite::getMenu();
if ($menu->getActive() == $menu->getDefault()) {
	echo 'This is the front page';
}

This works by checking to see if the current active menu item is the default one.

Joomla 1.6 and 1.7

The same code that worked in Joomla 1.5 will work in 1.6 onwards. However, since PHP 5 is now a minimum requirement for Joomla 1.6 the ampersand (&) is no longer required on the first line. Use the following code for a site where all content is in the same language:

$menu = JSite::getMenu();
if ($menu->getActive() == $menu->getDefault()) {
	echo 'This is the front page';
}

For multi-lingual sites the front page is dependent on the currently selected language, so you will need to use code like this:

$menu = JSite::getMenu();
if ($menu->getActive() == $menu->getDefault( 'en-GB' )) {
	echo 'This is the front page';
}
elseif ($menu->getActive() == $menu->getDefault( 'fr-FR' )) {
	echo 'Accueil';
}

For multi-lingual sites, it could also be necessary to display a specific code/html for all Default Home pages.

$menu = JSite::getMenu();
$lang = JFactory::getLanguage();
if ($menu->getActive() == $menu->getDefault($lang->getTag())) :
// some code
endif;

Hope this will help others.

Source: Joomla Documentation!

I have received some reviews and comments for this component. And I am trying my best to upgrade/add features as per the request and also fixing the bugs as pointed by the reviewers. Recently there was a request to add a feature for copying updated files to Override folder so that upgrade of Joomla language packs doesn’t overwrite the changes made. Also pointed one bug/issue that it was stripping the HTML tags. Now the issue has been fixed and added the feature to copy the updated language files to Overrides folder.

Updated:

- HTML tags are supported regardless of what tags are used. Since editing is performed in the administrator section, no validations are checked.
- Updated files will be stored in the override directory so that when upgrading the Joomla core will not overwritten the modified texts/language content.

Thanks Janaf for pointing the issues.

The latest and updated files can be downloaded from Joomla Extension Directory. Please do not forget to add a review when you install and use it.

If there is access to the server via SSH, then by running some MySQL commands, we can export and import large databases as well.

Export

Exporting a single database:
mysqldump -u [dbuser] -p [dbpwd] [dbname] > dumpfile.sql

Export all the databases in the server (rare case though useful in local systems sometimes):
mysqldump -u [dbuser] -p [dbpwd] > dumpfile.sql

Export whole multiple databses:
mysqldump -u [dbuser] -p [dbpwd] –databases [dbname] [dbname] > dumpfile.sql

Exporting specific tables:
mysqldump -u [dbuser] -p [dbpwd] [dbname] [table1 table2]

Restore

Restoring database is mostly done from a sql dump file. The same filename dumpfile.sql will be used here.

Restore a database:
mysql -u [dbuser] -p [dbpwd] [dbname] < dumpfile.sql

Restore a bulk SQL with multiple database:
mysql -u [dbuser] -p [dbpwd] < dumpfile.sql

Zipped files to be imported:
gunzip < dumpfile.sql.gz | mysql -u [dbuser] -p [dbpwd]

Restore multiple dump files using cat command:
cat dumpfile1.sql dumpfile2.sql | mysql -u [dbuser] -p [dbpwd]

Note: if your database user password has some special characters, do not use the password in the command itself. Just leave -p without password and you will be asked to enter the password when you hit the enter key to execute the command.
Example:
mysqldump -u [username] -p [dbname] > [backupfile.sql]

But this time I could not find VC6 version of PHP download. I browsed a lot and tried to search VC6 compiled PHP because I had already apache installed in my laptop downloaded from apache.org. Today I found there is a line just below that information in the same page as follows:

Do NOT use VC9 version with apache.org binaries, VC9 versions of Apache can be fetched at Apache Lounge. We use their binaries to build the Apache SAPIs.

Then I read the released note at http://windows.php.net/ and find the lines:

Windows users: please mind that we do no longer provide builds created with Visual Studio C++ 6. It is impossible to maintain a high quality and safe build of PHP for Windows using this unmaintained compiler.

For Apache SAPIs (php5_apache2_2.dll), be sure that you use a Visual Studio C++ 9 version of Apache. We recommend the Apache builds as provided by ApacheLounge. For any other SAPI (CLI, FastCGI via mod_fcgi, FastCGI with IIS or other FastCGI capable server), everything works as before. Third party extension providers must rebuild their extensions to make them compatible and loadable with the Visual Studio C++9 builds that we now provide.

All PHP users should note that the PHP 5.2 series is NOT supported anymore. All users are strongly encouraged to upgrade to PHP 5.3.6.

So I am now going to download the apache from http://www.apachelounge.com/ and will then use VC9 compiled PHP. I will update in my blog once I did.

मिति: २०६८, आषाढ २८ गते दिउसो ३ बजे तिर
स्थान: कमलपोखरी, हिमाल नर्सिंग होम अगाडी आँगनको गेट !
पात्रहरु :
प्रहरी: काजी उप्रेती (दर्जा – प्र. ज. – ट्राफिक प्रहरी)
चालक: म आफै (राजु गौतम)
महिला: मेरो श्रीमती

Thanks,
The Facebook Team
—————————————————————————–

And I was just wondered why and when I did request for resetting the facebook password. I never did that as far as I remember. And I just tried to login with my existign password and I was able to login. Thank god. This is again an SPAM. The spammers are with new route now. Facebook users are not almost awere of fake links to be clicked in the Facebook itself and they have now tried a new way by sending the links to their email address. As you can see above in the body part, they have asked to click on a link which MUST be a fake link or it MUST do an andesirable thing. I am not sure what exactly it does because I haven’t clicked it yet. But as far as I know the link does not even exists so I don’t think that it will do anything dangerous but to be safe it is good not to click on the links.

Seeing the email’s header part, we can say that it is the fake one:
Mail header:
————————————————–
from Facebook password+ys2yzf6@facebookmail.com
reply-to Facebook to Raju Gautam
date Thu, Jun 30, 2011 at 7:56 PM
subject You requested a new Facebook password
mailed-by facebookmail.com
signed-by facebookmail.com
————————————————–