jodurson
Forum Replies Created
-
@iovamihai, thanks for answer!
I hope that you will be able to integrate the field between plugins.
By now, temporary I will use a custom field to collect numbers.
Hi, @elliotvs!
Yep, I also thought of this today, I will perform deep scan and search for malware.
Thanks for the link on CF community, I’ll also take a look at what they write there.
Ok, @iovamihai, no problem, I’m try to explain. 🙂
When WooCommerce is activated on the website, a “phone” field appears in the user’s profile, the ID of which is “billing_phone”. This is a standard user field from Woo.
When creating a affiliate registration form through SliceWP – you can add various fields, for example, “Single Line Text” type.
It would be nice to be able to synchronize this field with the “phone” entity with Woo or to be able to collect by default not only emails, but also customer phones by default or through a optional field.
Forum: Plugins
In reply to: [Permalink Manager Lite] Set 404 on Default URIThx, @mbis!
Will try this snippet and will return with feedback if you have any questions.Forum: Plugins
In reply to: [Permalink Manager Lite] Set 404 on Default URI@mbis, yes!
At least just for all Default URI’s, not taking into the cases of coincidence of Default URI and Current URI.Forum: Plugins
In reply to: [Permalink Manager Lite] Set 404 on Default URIThanks for reply, @mbis!
I’ll try to tell you a little more.
In current development redirects are disabled on my site.
For some Woo product categories I create custom URI’s through the Current URI field. Sometimes it coincides with the Default URI and then there is no problems and not needed to create a 404 on the Default URI.
But when Current URI != Default URI – there go problem: both links exists. Previously, something in the plugin settings allowed us to send 404 from the Default URI.
I can’t remember what these settings were, even through the reverse actions.- This reply was modified 4 years, 7 months ago by jodurson.
@alexeypoltavets
Unfortunately, we did not solve this problem at full.
Two factors played: the lack of support from the plugin developer and the client’s unwillingness to engage in the project.
And I can’t see the project sources – the site has already been deleted and there are no backups left.
Sorry.- This reply was modified 6 years, 3 months ago by jodurson.
Thx, I’ll check it later and give you a feedback.