Hello Support Team,
I have a fresh installation. Unfortunately, the Statusbar loads extremely slowly. I can't find any mistakes.
Can you help me, please?
Lg
Herbert
HI, Herbert.
Thank you for contacting us.
What JomSocial version do you use?
I can't check myself as your backend is htaccess protected.
Please, edit your first post and add htaccess credentials.
Hi,
Sorry, I missed that. I have added the access data.
I am using the latest version of JS (4.5)!
Lg
Herbert
Hello Support Team,
May I ask whether there is a solution?
The mistake is not comprehensible to me and therefore I am dependent on your help.
With many thanks
Herbert
HI, Herbert.
I tested your site on FireFox Quantum and it loads quite fast for me:
prntscr.com/hgowyo
About 10 seconds to full load but status bar and all elements are visible nearly imminently.
What browser do you use?
Hello, Michael,
that's strange. I use the current Chrome Browser. The effect can also be seen on the smartphone and it do not only affects the status bar! Shared images first displayed as single image and then as Collage.?
Greetings Herbert
HI, Herbert.
Chrome recently released new versions and after that other users also reported this issue.
But it was fixed in 4.5.
Could you try with other browser than Chrome? Just for test.
Hello, Michael,
the bug really seems to be related to Chrome!
With Firefox the site loads normally!
However, I already used the current JS 4.5?
Is there a solution?
Thank you very much
Herbert
HI, Herbert.
There ware some changes in Chrome 62 and we're working on fix.
But issues are gone with Chrome 64.
www.techworld.com/download/internet-tool...ev-64032693-3249557/
HI, Herbert.
Please, take a look at this:
www.jomsocial.com/forum/installation/379...-php-not-used#182893
Good morning,
Thank you very much for the interesting links. The commenting out doesn't work for me:
"components/com_community/templates/jomsocial/layouts/stream/comment. php"
<img src="#" alt="attachment"> on line 82
Best regards
Herbert
HI, Herbert.
Hmmm, bug is in Chrome so sooner or later they will fix it as it's not present in Chrome 64.
I'm afraid that's all I can help here :(