GHES
Forum Replies Created
-
Update: By not putting any URL in the field, but just the anchor ID, the page goes to the footer on submit, but to the footer on the home page, not the page the user accessed the registration form.
This is a shame, as it means the user has to claw back to the point that caused them to want to register. In other words, it leads to user frustration.
Actually, I spoke too soon. That works on my test site, but not my actual site.
I get the message:
Error
This page can’t be displayed – your request has been denied for security reasons.
The incident ID is:[ …..]So what I need hasn’t been solved after the update.
Thanks borisv for giving it a go.
Regrettably, I can’t include a snapshot of the fields I’m referring to on the ‘Edit User Role‘ admin page when you create a new user role.
They relate, though, to the ‘Registrations Options‘ panel on that page.
I have, however, solved it.
for ‘Registration Status‘ I selected ‘Auto Approve‘;
for ‘Action to be taken after registration‘ I selected ‘Redirect to URL‘;
and for the ‘Set Custom Redirect URL’ field, I entered
<?php get_permalink(); ?>/#footerThis works. Before the recent update I was getting an ugly error message, but no longer.
So you are right. I only had the get permalink part before, but by adding the anchor ID the page not only refreshes, but now returns to the same spot.
I hope that makes what I needed to achieve more clear.
But it works, now, anyway.
Forum: Plugins
In reply to: [Stripe Payment Gateway WooCommerce Addon] Undefined index: stripe_tokenThis is truly the best Stripe/WooCommerce plugin as I did get it to work brilliantly before.
This time, though, it’s different and after your first response I did stuff around some more, but we decided to ditch the whole WooCommerce side of things to use Stripe directly.
Thanks heaps for your assistance,you’ve been on the ball the whole time. I expect your solution above with help someone else.
Thanks
Forum: Plugins
In reply to: [Stripe Payment Gateway WooCommerce Addon] Undefined index: stripe_tokenYes, followed the first instruction, deleted previous version and re-downloaded the plugin from WordPress.
All the Stripe API keys are added. I even had the site owner check if there were new updated version of his Stripe keys, but no.
Let me try some things.
Forum: Plugins
In reply to: [Stripe Payment Gateway WooCommerce Addon] Undefined index: stripe_tokenI’m unable to see why, but the debugging error now reads: Parse error: syntax error, unexpected ‘)’ in /[…]wp-content/plugins/stripe-woocommerce-addon/stripe-woocommerce-addon.php on line 377
Line 377 is the closing
);I commented out line 374 as well, which allowed the site to load.
Retried transaction, returns to debugging error: ‘Undefined index: stripe_token in /[…]/wp-content/plugins/stripe-woocommerce-addon/stripe-woocommerce-addon.php on line 346’
Maybe, contrary to WooCommerce’s procedures (i.e. their recommended use of functions to disable fields), you can’t get rid of unnecessary fields for a gateway to work.
Forum: Plugins
In reply to: [Stripe Payment Gateway WooCommerce Addon] Undefined index: stripe_tokenThanks, will try …
hi – wonderful plugin – thank you – yet although I am up to scratch with version 7.0.29 – the plugin is still causing my whole site to load much slower.
Any suggestions on how to fix this would be much appreciated.
Odd – my only suggestion is it may have something to do with the parameters you have ticked. I have ‘Show the field in the registration’, ‘Show the field in User’s profile’ and ‘Show the field in Users Extended section’ ticked (users can’t actually access their profile as I want them to stay on the front end, but I still have it ticked). If it’s not that, then maybe it’s another plugin you have but I don’t that’s preventing the extra fields’ inclusion. You’d have to do one of those laborious plugin checks.
This stuff’s frustrating, so hope you find an answer after any toil.Yeah – I just don’t want to go there. My previous website was hacked. I’m doing everything, this time, to eliminate any gates left open – such as un-updated plugins. Being hacked it too painful.
Theme My Login hasn’t been updated to the current version of WordPress. I’m steering clear of non-updated plugins. Plus, I read somewhere that it too is incompatible with certain functions of your plugin.
Many thanks, though, for responding.
No – I mean if one sets up front-end login and registration so that a new user doesn’t leave the site but stays on the page, even if this front-end login is achieved through WordPress coding rather than a third party plugin – when the new user is sent a confirmation email generated by your plugin, the link takes them off site to WordPress’s login. For new users unaware of WordPress’s workings – it looks as though they have been sent somewhere entirely foreign, not the website they just registered for.
No – which means it’s incompatible with Login with Ajax. Annoying, as that plugin solves other problems.
One last thing, is there anyway the new user can be sent a link to a site’s custom login – rather than to /wp-login.php ??
Thanks. I tried a few things again today, but still no luck.
I’m using the latest version of WordPress, the latest version of your plugin (just downloaded) on a Safari v5.1.4 browser (in case that makes any difference).
The registration form is generated by the plugin Login with Ajax (latest version).
As the checkboxes don’t work, I’m using drop-down menus instead that work perfectly. So I don’t know if a visit to my site it is of any use, but … (in case) … https://gailhastings.com.au/ (and click REGISTER bottom left of footer).
I guess, if you’re at your computer now-ish and you let me know – I could change the drop-down menus back to the checkboxes and you could try registering and see for yourself.
Brief update: Tried the line you sent – but it broke the site.
Turned on debug mode again to see why – the message read:
Parse error: syntax error, unexpected T_IF, expecting T_STRING or T_VARIABLE or ‘$’ in /usr/local/pem/vhosts/106347/webspace/httpdocs/wp-content/plugins/wp-members/wp-members.php on line 140
Not my wordpress day today.