My Continue Shopping Button Has Resurfaced!

[personalityjunkie]

Greetings,



I'm a bit baffled because, for a while, I was successful in removing the continue shopping button from my cart, now it has suddenly reappeared. I've done all I can to troubleshoot, but to no avail.



I'd really appreciate any help:



http://personalityjunkie.com/ebooks/



Note: The View Cart button code is on the page, but I've replaced the image with an inconspicuous period.

[E-junkie_Monster]

It looks like there is some code on your site that is already using the jQuery object that was also used to remove your Continue Shopping button, that can cause conflict and make the cart customization ineffective.



Fortunately that can be fixed without much hassle, see our troubleshooting page here:

http://www.e-junkie.com/ej/trouble.custom-cart.jquery.htm

[personalityjunkie]

Thank you for your quick response.



Unfortunately, I tried both options suggested on the page you referenced and neither seems to be working. The "force" option is currently implemented:



http://personalityjunkie.com/ebooks/

[E-junkie_Guru]

The problem appears to be that your View Cart customization code is all on one line in your page including the HTML comment lines <!-- and //-->. There at least needs to be a line break after the <!--, so the function EJEJC_lc(th) ...etc. starts on a new line. In fact, you can just delete the <!-- and //--> parts entirely, since those were only ever needed for really ancient browsers that nobody uses anymore.

[personalityjunkie]

Okay,



So I made no further changes and the continue shopping button is suddenly gone again (hurrah!). My site did have an automatic Wordpress update, however, which I suppose could have somehow contributed.



Anyway, thank you so much for your help, you guys are always quick responders!

[E-junkie_Guru]

Looks like the cart customization code in your page has been reformatted into separate lines again, so if you didn't do that yourself, likely your latest WordPress update fixed the problem that a prior update probably caused in the first place.