- This topic has 7 replies, 3 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
Very green to this:
The fly-out menus from my shopping cart page work just fine. But if you click on my “store” page itself, I get a “HTTP 402 Forbidden…”
The main page is here: [www.eyepoppingphotos.com]
In the store page I see this code: [WPS_store_home]
If you go to the “pages” menu from admin dashboard, do you see the “Store” page as published? I have a feeling you changed the status of that page to a “Draft” status. Or you have another plugin that is not letting you render that store page for some reason (it is a standard WordPress page with a shortcode in it).
It says “published.” The sub menu pages to “Store” work fine (such as “Cart” & “Checkout”) but not the actual “Store” page. I’m also running Photocrati but I added your plug-in because I like it better than the shopping cart option offered by Photocrati.
It appears that your server setup has some kind of firewall rule which is causing the forbidden message.
Can you ask your host provider to check if they have any .htaccess or other security rules which are preventing people from accessing pages with a slug called “store”?
My server changed something & now I get a page see [http://www.eyepoppingphotos.com/store/]
But I suspect that’s not what I’m supposed to be seeing. What should my “Store” page look like?
You should see a standard WordPress page (with your header, sidebar, footer etc.). That is definitely not what you should see. I have a feeling there is something else that was installed there before and parts of it is still there. Tell your hosting provider, why can’t you see that WordPress page (it is just a normal wordpress page).
Prior to purchasing Photo Seller I purchased & installed Photocrati. I was told by someone from WP Photo Seller that there wouldn’t be a compatibility issue. Is it possible that that’s where the problem lies?
I was told by someone from WP Photo Seller that there wouldn’t be a compatibility issue. Is it possible that that’s where the problem lies?
The photo seller plugin does not have anything that would cause a conflict like this.
By looking at the way that page is displayed, it is obvious that the wordpress code is not even being executed. You have something on your server which is rendering this page before wordpress even has a chance to run.
- You must be logged in to reply to this topic.