JA Builder Pro & Jomsocial Toolbar Socialize login Mobile popup opens and then closes immediately without possability to login
Every page that JA builder is used, the socialize login popup box in Moduule "Toolbar" on mobile device "In this case Samsung j5) doesn't remain open once clicked.
It disappears
The socialize toolbar popup box on other pages where JA Builder is not used it works fine.
Hi Lee,
Please you disable JA Builder, because that plugin is not be used if you use socialize.
thank you!
I am sorry?
There is obviously a misunderstanding, the JA builder plugin is not compatible with jomsocial?
All that is not working is the pop up login box in mobile view on mobile device as mentioned, a javascript conflict,
so best solution
Disable and do not use JA plugin.
Well, I have created around 5 pages with that plugin, now I have to recreate the pages with other method.
Can can please just fix the conflict that is stopping the login box popping up? Please?
Thank you
HI, Lee.
I apologize for misunderstanding.
If JA Builder do not work with Socialize now we'll make it work in nearest future.
I'll report that issue to our developers so we could provide you a reliable solution.
Hello Lee
We checked the issue on the fresh package and unable to replicate it.
Kindly edit your first post and submit
Admin URL:
Admin Username:
Admin Password:
FTP Server:
FTP Username:
FTP Password:
let me know with a reply in this post, once you will add these details.
I cannot allow access at this moment, but you are welcome to go to the url and see the issue for yoruselves
Moblle device used
Samsung J5 latest android official firmware
Steps to reproduce
1. Navigate to
www.speakeasyenglish.org
on mobile device
2. Clcik login "top right"
3. See that login box opens then disappears immediately
4. Check console "Google chrome"
5 I think you know the rest of the story
Let me know once you have checked the issue on the mobile device
As I said I cannot grant access to admin at this time.
But you can replicate the issue and see what is causing it from console
Thank you
Please update
HI, Lee.
Pankaj already replicated this - that's why he needs all the other credentials - to investigate this further.
Please, read our declaimer here:
www.jomsocial.com/support-policy
Right under main table.
Without credentials we could only nod our heads and say - "yup, mate, your site have issues"... but I guess you rather prefer to have it fixed, right? :)
In that case:
Please:
1. Edit your first post.
2. Click switch below main text field:
prntscr.com/fk3hdg
3. Provide your site details: backend URL, admin credentials and FTP:
prntscr.com/fk3hwz
4. Let us know that you provided credentials by posting in the same thread.
I would not like to say that you "would" copy (Protected) private information. It is just that I am obliged by Italian law to do everything in my power to avoid the potential of exposure to sensitive data, otherwise I could simply be sued. . What can we do?
Tell you what, you give me access to jomsocial admin then I will do the same on my end :-) Please forgive me, but it is the very same argument right? Not that I am asking for access
HI, Lee.
Replication is not fixing :) Even if you replicate the issue - without access, you can't fix it.
Do your site user experience this issue? Can they fix it? Nope - without access how could they? :D
I think that much better than playing ping-pong is to create site copy without sensitive data. I know EU law for personal data protection so I know that you're obligated to protect them.
We talked via PMs so I hope we have agreement here. Do we? :)
Hi
JA Developer Fixed the issue on your site. The issue was due to duplicate Bootstrap.js file on site.
T3 and Builder both using the script that creating this issue, So developer added a fix to prevent the loading of bootstrap.
Path: /plugins/system/jabuilder/helper
Got to line go to line 1095 and add this code below
if ($url == 'lib/bootstrap/js/bootstrap.min.js') {
continue;
}
Here:
prntscr.com/halwv4
We will add the fix in the next update.
Regards
of course we have an agreement, Michal, your questions are valid, but unfortunately this does not answer the enevitable question....
Anyway, seems that there has been a fix recommended by developer, I will appy that fix.
By the way, if my visitors could fix the issue, then I would ask them to develop the component, but because you guys are the best, of course I come to you! :-)
Thanks
HI, Lee.
Certainly we are the best :)
The only questions should be always: "if we could fix it" and "when it will be fixed" :)
No need to argue about anything else ;) In future if you encounter an issue, please, create copy so we could investigate on it - without access to customer sensitive data.