Yes I saw that in your notes. I know it doesnt need an override, but the override from the previous version of your module was still there. I opened it up and it mentioned ets in there so I deleted that override. Not sure if you can put something in your install file to remove that override for people who are less savvy
I just thought double protection may be good. I don't have a single registration or contact form submission since disabling the recaptcha module, so looks like just yours alone will do the trick. No need to go through the hassle of remaking it without the override.
And since disabling the recaptcha yesterday, I now have 136 entries in the SS Action, which I never got before.
Im not sure when this happened, but this module and the ReCaptch module are now conflicting.
This is stopping anybody being able to log in as it throws an error like this
{“error”: true, “message”: “404 not found!”},
Ive disabled the Recaptcha one for now and its working again.
Thank you Andrei,
the "if" statement is working fine now, and the search is also working fine.
The word "for" was in the fuzzy search word list to ignore so I removed that and it worked but showed lost of results so I changed that tag to "3-for-£30" and its working fine. (https://www.northwestecigs.uk/disposable-vapes/558-1786-lost-mary-bm6000-disposable-vape-2-nic-salt.html#/432-flavour-banana_volcano)
Many thanks
Hi Andrew,
thanks for your reply.
I have only added that above code to my product.tpl. If I remove the “if statement” then the rest of the code does show the tag correctly and makes those links, ie “/search?tag=3+for+£30”
But it showss an empty tag, when the product has not tags.
This is what I currently have.
{if $product.tag|@count > 0}
<ul class="tags">
{foreach from=Tag::getProductTags(Tools::getValue('id_product')) key=k item=v}
{foreach from=$v key=lang_id item=value}
<li><a href="{$link->getPageLink('search', true, NULL, "tag={$value|urlencode}")}">
{$value|escape:html:'UTF-8'}</a></li>
{/foreach}
{/foreach}
</ul>
{/if}
Its the first line that must be wrong.
Maybe I need to count the tags and put them in a variable so I can just use it like this.
{if $producttagcount > 0}
Ive actually changed it back to 8.1.29. Not because I had any problems but the PS advice says the compatability does not go up to php 8.3.9 yet so unsure on updates.
Module is now showing the columns, First Name, Last Name.. but they are all blank.
and the columns are now too wide. Can the password one be removed. I dont think that is of use to anybody.
Works fine on my 8.1.7
Im always afraid that is potentially blocking legitimate registrations.
Would it be possible to maybe add columns for Name/Surname and remove the password hash column ( as I think that column is useless ).
Then if we see a Name/Surname that looks legitimate we can have an option to authenticate that registration and send the email registration form to the customer with a custom note (ie, Upon registration, your ip address was mistaken as a potential bot registration. We have now activated your account and you are able to log in".
Thanks for a great module