Magento Fix on simplexml_load_string error at lib/Varien/Simplexml/Config.php

If you’ve noticed that your system.log’s size is increasing every minute because of the error logs like this:

Warning: simplexml_load_string(): ^ in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): Entity: line 292: parser error : expected '>' in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): nkey.png</233><234>manufacturers/image.jpg</234><235>manufacturers/image.jpg</ in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): ^ in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): Entity: line 292: parser error : Opening and ending tag mismatch: config line 1 and unparseable in /lib/Varien/Simplexml/Config.php on line 383
2016-06-27T14:01:04+00:00 ERR (3): Warning: simplexml_load_string(): nkey.png</233><234>manufacturers/image.jpg</234><235>manufacturers/image.jpg</ in /lib/Varien/Simplexml/Config.php on line 383

Then consider your problem solved. After hours and hours of googling and searching at stackoverflow, I found nothing. Most of the solutions to the problem that is related to the simplexml_load_string error is something that is related to an XML file. But my problem wasn’t.
Continue reading “Magento Fix on simplexml_load_string error at lib/Varien/Simplexml/Config.php”

git: User was holding a relation lock for too long

Screen Shot 2016-06-16 at 10.06.11 AM
If you encountered this error while pushing your recent change to your git repo, worry not. You’re not alone. Just recently, like a few minutes ago, I’m having trouble pushing my latest commit to my Bitbucket repo. Good thing I found out that it’s just a bitbucket issue, not really an issue with my repo or with my server or with my localhost.

Below is the exact error I’m getting while trying to push my latest commits:
remote: canceling statement due to conflict with recovery
remote: LINE 1: …er”.”date_joined” FROM “bb_repository” INNER JOIN “auth_user…
remote: DETAIL:  User was holding a relation lock for too long.
! [remote rejected] master -> master (pre-receive hook declined)

I actually tried pushing it again and again, switch branches, cloned a new repo, but no can do. Nothing I tried worked, it’s because Bitbucket is having issues, not me. Haha!

Let’s just wait for Bitbucket to fix the issue and not panic.

Google Adsense cannot login using Chrome, but in Safari, you can!

adsense-cannot-login
If you’ve encountered this issue last year, it seems it’s still not fixed. When attempting to sign in via adsense.google.com using Google Chrome, you’ll be prompted with this error message: “Looks like this Google account isn’t associated with an AdSense account. That’s okay. You can either sign in with the Google account associated with AdSense, or sign up for an AdSense account today.”. I thought this is just temporary. All I know is that Google is signing in your Adsense account using an individual account data, not your actual account data. This happened to accounts who signed up with Adsense prior to the implementation of Google Single Sign-on. So it’s prompting that your email is not associated to Adsense at all.
Continue reading “Google Adsense cannot login using Chrome, but in Safari, you can!”