nadworks

avadhut2013, can you post the solution since you’ve resolved this, please?

Same here.

Exactly the same problem (and question) here.
If there’s only one option, it should be automatically selected and added to the total. Bam.

… it would also be helpful to have some sort of a “restore default” or “reset” button on the Checkout Settings page. Looks like once I’ve deleted a certain field (i.e. shippingcountry), I cannot get it back. I can only create new fields, but they don’t restore any of the standard labels.

Thanks, Justin.

I have not knowingly received anything from GitHub inviting me to test the improvements. Apologies for appearing desinterested. I am not actively following your developments but would be more than happy to receive updates. If you are running a mailing list for your users, I’d be happy to subscribe.

Here, I was simply responding to yet another user on this forum with this very problem that I have been having for over a year. FYI the solution above still works well. I have just implemented it on the latest version I am running (WPeC 3.8.13.4 and Gold Cart 2.9.7.7). My pages break without this little hack.

Glad you have fixed it. Looking forward to installing the official release as soon as it becomes available. I’m not a great fan of WPeC Betas – have had some bad awakenings in the past.

Justin, I am puzzled why you guys – after over a year of this issue not only having been reported via bug reports, but also been reported together with a solid solution – have not been bothered to include it in a release. It’s interesting to me that you rather disgruntle users and allow for their pages to break after upgrades, than simply fix this annoying issue.

It happens to me each time I upgrade, and each time I have to manually edit the core files to fix it:

Shortcodes ignore the custom category view that comes with Gold Cart. Everything reverts back to default view.

THE SOLUTION:

Go to
/wp-content/plugins/wp-e-commerce/wpsc-components/theme-engine-v1/helpers/page.php

…and find (around line 508)

$saved_display = wpsc_get_customer_meta( 'display_type' );
$display_type  = ! empty( $saved_display ) ? $saved_display : wpsc_check_display_type();

replace it with

//$saved_display = wpsc_get_customer_meta( 'display_type' );
//$display_type  = ! empty( $saved_display ) ? $saved_display : wpsc_check_display_type();
if ( isset( $_SESSION['wpsc_display_type'] ) )
$display_type = $_SESSION['wpsc_display_type'];

That’s it.

It has been part of the bug reports on (I think) Github for over a year, accepted by the developers and many users. But nobody seems to be keen to implement and release it.

Same problem after re-installing latest beta version from GitHub:
ERROR: ZipArchive returns status: (ER_DELETED) Entry has been deleted
Giving up after 5 tries now. This just isn’t working at all. Shame.

Wow, thanks omungal. Yes, the 404 detection is really the worst feature of this plugin. The amount of time I have wasted getting access to my own website is borderline ridiculous. Too many plugins and actions trigger the log out and the whitelist is indeed pointless in those instances.

A little more testing on their behalf would be a good idea.

Same here. Unable to log into my own site and desperately trying to find the whitelist in the database tables…

Same problem here. Need occasional cron jobs for backup triggers and mailings. With iThemes Security blocking repeat failed login attempts, Cron Jobs trigger lock outs.

Feel this needs to get fixed.

That’s strange the file is there
https://domain.com/wp-cron.php

Same problem here.
But ALTERNATE_WP_CRON didn’t sort out y problem either.
Instead I am not being forwarded to a 404 page on my site
https://mydomain.com/wp-cron.php?_nonce=d731004d1a&jobid=1&backwpup_run=runnowalt

Exact same problem as snthorv. Editing pages and suddenly get logged out. Don’t care if this is due to a plugin or my Firewall, or my server. But the fact that I am getting blocked from logging back in is due to Better WP Security, and whitelisting mi own static IP would easily solve this.

Absolutely desperately needed!

Whitelist for failed logins is essential, guys.

So, you have launched yet another upgrade without taking care of this? AGAIN we have to manually hack the core files to fix our sites?

I am flabbergasted, guys.