Hi!
In Chrome Console, there is always a message that alerts me about a password field:
[DOM] Password field is not contained in a form: (More info: https://goo.gl/9p2vKq)
<input class=”td-login-input” type=”password” name=”login_pass” id=”login_pass-mob” value required>
The thing is, I do not have a password field in my website, and I already have disabled the login/sign in modal in Theme Panel.
What should I do about this warning? Is there a way to Newspaper not to load this modal?
Hello !
Please provide us a link to your website and a screenshot of this error and where exactly you see it. We will investigate and see what can be done.
Thank you !
Hi, Vlad!
The link for my website is in my profile…
But here it is: https://osaopaulo.org.br
Here is the screenshot of the error: https://paste.pics/BG34A
And you can see it exactly in any and all of the pages of my website…
As a matter of fact, also in yours.. Here goes: https://paste.pics/BG34V
Sadly, this fact urges me to think that the coding of the theme is poorly done, and was never reviewed or debugged…
Hello !
I have inspected our demos and this doesn’t seem to be present as you can see here: https://www.screencast.com/t/UlniAXfn I have tested this on my localhost too and again this is not present. Testing this on tagdiv.com will not be relevant since it was custom built.
Please check if you have the standard pack plugin deactivated and re-inspect after you disable the plugin. This should fix the issue.
Thank you !
Hello, Vlad!
No, I do not have the Standard Pack active (nor installed).
In fact, I’ve built the whole site with Tagdiv Composer and Tagdiv Cloud Library..
Is there a way to disable this login thing?
Ah! And sorry to inform you, but this warning is present in both standard and PRO demos on your server… here are the screenshots to prove it.
https://demo.tagdiv.com/newspaper_pro/ -> https://paste.pics/BH3N9
https://demo.tagdiv.com/newspaper/ -> https://paste.pics/BH3LJ
Hi,
Indeed in our code for login is no form set, as I see on some articles this can be fix adding the form tag https://www.codetd.com/en/article/6890779 also I noted this on our list to be checked and find an solution to remove those warnings.
Thank you!
Ok, Calin. Two questions about it:
1) Where do I put this code? I’d be glad if you can inform the location.
2) More importantly, is this a way to disable the login thing, as I do not use it, and already disabled it in the Theme Panel?
Thank you!
Hello !
Pleas add FORM in this 2 places:
– wp-content/plugins/td-cloud-library/parts/tdb-login-modal.php
– wp-content/plugins/td-cloud-library/parts/tdb-login-modal.php
And added like this: https://i.imgur.com/3TXj7x2.png
If you want to remove it simply comment it using //
Let me know the result !
Thank you !
Hi, Vlad!
It worked a little; now Console asks this:
[DOM] Input elements should have autocomplete attributes (suggested: “new-password”): (More info: https://goo.gl/9p2vKq) <input class=”td-login-input” type=”password” name=”login_pass” id=”login_pass-mob” value required>
But, let me ask something: Is there a way to make this element not o load?
<div id=”td-mobile-nav”>
It is the mobile menu, that is loaded in desktop view.. I don’t need it, as I am using Mobile Pages for the mobile version (and thus it is not needed to load..)
Hello !
For the password input please add this piece of code: autocomplete="current-password"
Also in order to stop the mobile menu code you will need to comment it out here: wp-content/plugins/td-composer/legacy/Newspaper/parts/menu-mobile.php
Thank you !
If I comment this code, won’t it prevent from openning the menu in mobile, also? Or only on desktop?
Hello !
I have went and tested this out as you can see here I completely removed that piece of code from here: https://www.screencast.com/t/1nmuMn56Tt
After saving this you can see that <input class=”td-login-input” type=”password” is no longer available and also the mobile menu works perfect.
I hope this was helpful !
Thank you !
Hi, Vlad!
I took the same piece out of my code (https://paste.pics/BIFMG), but got no results:
– The console warning is triggered (as seen in this screenshot: https://paste.pics/BIFKO)
– and the element is still being loaded in the front-end of the site: https://paste.pics/BIFLN
As always, after editing the code, I flushed all caches: cdn, server, plugins, browser…
Is there any other code/place to edit out?
Hello !
Please make sure to restore your commented file and please comment everything that is contained in this 2 files: wp-content/plugins/td-composer/legacy/Newspaper/parts/register.php and this one wp-content/plugins/td-composer/legacy/Newspaper/parts/header/td-login-modal.php
This should fix the issue and also lead to no errors.
Please let me know the result on your end.
Thank you !
Hi, Vlad!
Thank you for directing me to the correct path!
Indeed, the warnings in the console are gone. Thanks!
Only one thing: as you can see in this screenshot (https://paste.pics/BJBUU), the mobile elements are yet being loaded… I do not need them (as they increase the DOM elements loaded and the fact I am not using the responsive layout, but the Mobile Pages) and thus I ask you if is there any way to remove this items, without corrupting the Mobile Pages.
I could comment out the div classes that are being loaded, but I think this is going to break the mobile pages. Am I correct?
Thanks!
Hello !
In fact, commenting the divs should do the trick. You will have to test this but what is done in TagDiv Composer is saved in the database and should work.
Let us know the result !
Thank you !
Hello, Vlad!
Sorry for the late reply, but only now I tried to do the commenting out of this divs.. Surprise, surprise: it didn’t work! Commenting out the divs broke the layout before the header of the site…
Hi,
Please send an email at contact@tagdiv.com and provide wp-admin and Cpanel access, so we can investigate this issue and find a great solution for you. Also paste a link to this topic so we can easily identify you.
Let us know and we will gladly assist you.
Thanks!
Hi, @bettina!
After 10 days of walking in circles, here is the answer support team gave me:
“Since those elements are used on desktop too, no, you can not remove them. Or if you remove them will remove from everywhere (mobile and desktop).”
Why you made me send an email with credentials when you could easily have answered me here, in the forum, is beyond my understanding, but, at least now, I know that I should not be bothered to improve my website with this theme…
Thanks!
Hi,
I’m sorry that you felt bad using our theme and our services. But, we are trying to help you all efficiently and without delaying the time as much as we possibly can.
Sometimes, for solving an issue, we need also some extra information to understand exactly the problem and provide you the right fix in the right time. That’s why, I suggested you to send an email directly, so we can see directly the issue that you have and last but not least it could delay more or less because it depends on our communication and understanding with our clients.
Thank you for your understanding!
Have a nice day!
Hi, @bettina!
Sorry for let my frustration out on you…
I too am trying to solve the issues that appear in my site, but at times it seems that the support are a little bit shady in trying to help, almost seeing the user as an enemy, not a partner… I mean, the more directly the better, as time is precious (even more in the internet!). Sometimes the support seems to stall us (and I hope it’s not intentional) asking things that were already answered, or not answering things that were asked, losing time for both sides.
Anyway, sorry again for misbehaving.
Have a nice Easter!
