-
Hi, my name is Alessandro and I just purchased this plugin from code canyon.
I am facing several issues using it in my website:
the website is newsreel.com and you can see the issues navigating to my profile -> login / register / login (last one is modal).
1) When trying to login I get a SyntaxError: JSON.parse: unexpected character using firefox, SyntaxError: Unexpected token < using chrome
I get that error also if I click the login button in the registration page.
2) Modal login/registration pages doesn’t work (Only an empty lightbox appears.)
3) When using twitter register/login I get
Notice: Undefined index: oauth_token in /home5/forexazi/public_html/newserex/wp-content/plugins/userpro/lib/twitteroauth/twitteroauth.php on line 80Notice: Undefined index: oauth_token_secret in /home5/forexazi/public_html/newserex/wp-content/plugins/userpro/lib/twitteroauth/twitteroauth.php on line 80
and the page just refresh
I guess that’s because my twitter app is read-only mode. Can you confirm?1) When trying to login I get a SyntaxError: JSON.parse: unexpected character using firefox, SyntaxError: Unexpected token < using chrome To fix this issue, please change theme/disable other plugins until you find the conflicting plugin please.
Hello, but what would you suggest if I could not disable plugin that conflicts with userpro as for example in my case the conflicting plugin is the core of my website.
Hi Superbobrik,
if you have found the conflicting plugin you should notify the author of that plugin about this issue. Most times they are happy to fix it.
Please also post the the conflicting plugin here as a reference so that Ahmed can have a look, thanks.
Please post the plugin name here so I can get an idea about which plugin causing this conflict. Also it’d be good to contact the author as keyhanjun suggested
Hi, deactivated all my plugins one by one and nothing. Reverted to default theme and still the error persist. Please take a look at my web page
It’s not possible that you get the syntax error after disabling everything, there must be a culprit. The plugin by default does not trigger this syntax error.
You must be logged in to reply to this topic.