You are here:  » jump.php issues


jump.php issues

Submitted by Rob Moffatt on Mon, 2015-11-02 09:48 in

Hi David

I have successfully installed the PT backend for a WordPress installation and everything is working without problems - searches, merchants, categories, brands and jumps to the seller are all fine with the clicks being registered and shown on the admin page.

I followed the instructions for the PTO WordPress plugin and am able to display featured products, search and the links to merchants, brands and categories without any problem.

However, when clicking on the link to the seller, the page hangs and I notice that the jump.php id for the same product was different from the working link in the backend.

After reading around the forums, I set the $config_useTracking to FALSE and ensured the permalinks were numeric - the link to the seller worked without any problems inside the WordPress front end (obviously the clicks are not registered in the PT backend!)

Why do you think this is happening?

Please see below the website's URL, the PT (working) backend link and the non-working WordPress link:

{link saved}

{link saved}

{link saved}

Many thanks for your time -

Best wishes,

Rob

Submitted by support on Mon, 2015-11-02 10:08

Hello Rob,

I wonder if inadvertently they are looking at different databases - the reason I wonder is that I notice that your shopping page (the container page that has the [pto] permalink) is showing Featured Products, yet if I browse directly to the Price Tapestry installation at /pt/ the Featured Products are not shown...

If you edit pt/config.php and double check that the $config_database... settings match the equivalents from wp-config.php you should then find the same Featured Products being displayed on the /pt/ home page and links then working as expected...

Hope this helps!

Cheers,
David.
--
PriceTapestry.com

Submitted by Rob Moffatt on Mon, 2015-11-02 11:02

Hi David

Many thanks for your speedy response!

I checked again - and you were absolutely spot on - there was an inconsistency between the two database prefixes, these have been repaired and everything is working perfectly with both the WP frontend and the PT backend.

Much appreciated!

Best wishes,

Rob