MageAdventure.com
Maria's Journey On Internet Marketing With WPMage!

 

Editing phpBay & XSitePro .htaccess File

After one week that my ePN website was accepted, I bought phpBay API & WordPress plugin to create eBay ads. The phpBay API is useful only for my xsitepro sites and since most of my sites are built with xsitepro with blog added on them, then, the phpBay WordPress plugin can create eBay ads on the blog. At the moment, I am working on the phpBay API. There are couple of tutorials on the net on how to make phpBay and xsitepro websites work in harmony with each other but the xsitepro tutorials show on how to create hundreds or thousands of pages based on keywords entered at Multi Page Creation Wizard. This shows pages after pages of eBay ads in an instant but the pages are all eBay ads.

I don’t like that way because I want the eBay ads to appear after the article content of the site’s web page. The phpBay API manual, however, shows on how to do that by placing the php code anywhere I want the eBay ads to appear on the web page and editing the .htaccess file.

When I edited .htaccess file, the website has Internal Error 500. So, I reverted back to the original .htaccess file and my website comes alive again. While researching why my website has Internal Error 500, I found the following answer right from hostican.com’s (my host) knowledgebase for cPanel Shared Hosting Internal Error 500. If you encounter the same, this might be the solution to your problem.

Here’s the suggestions for Internal Error 500:

  1. Check your .htaccess file. This is a file that resides in your /public_html/ folder, and can often cause this error, because the syntax within this file is incorrect. Simply renaming it, can often fix the problem (and then you will need to see what the issue is within the contents of this file).

  2. Check that your files don’t have permissions of 777. Since we run PHP as CGI, this means that your permissions can not exceed 755. If they are more, then this can also trigger the Error 500 (Internal Server Error). Simply changing the permissions on the files / folders that have been set as 777 down to 755 will fix this issue.

  3. Check that your /public_html/ folder doesn’t have permissions greater than 750. This can happen, when you accidentally change the permissions on this folder without realizing it. If its anything other than that, simply change it back, and this should resolve this issue.

I tried the solutions as suggested above but my website still has Internal Error 500 everytime I added the .htaccess code of phpBay API. Thus, I just reverted to xsitepro’s .htaccess so that the website is online and wait for the response of hostican senior admin because I submitted a ticket regarding this issue.