Experiencing a 401 Unauthorized Error During Update?
If you're seeing a 401 Unauthorized error when trying to update your Joomla extension, it's likely due to our new two-factor authentication (2FA) security measure for your Download ID.
To resolve this, check your email (Spam folder?) for a message to approve your server or device, or read our detailed blog post here(
onlinecommunityhub.nl/best-practice/new-...-extension-downloads) to understand the steps involved. This will guide you through approving your server for future updates.
No bug Plugin does not do anything
- Peter Klinke
- Onderwerp Auteur
- Offline
- Berichten: 9
- Ontvangen bedankjes 0
Graag Inloggen deelnemen aan het gesprek.
- Ruud van Lent
- Offline
- Berichten: 1624
- Ontvangen bedankjes 107
Thanks for reaching out.
Is the plugin enabled?
Did you configure the advanced settings to eg only create images when logged in with specific user?
Do you have a frontend url that I can check?
Currently on vacation so response time is slow
Graag Inloggen deelnemen aan het gesprek.
- Peter Klinke
- Onderwerp Auteur
- Offline
- Berichten: 9
- Ontvangen bedankjes 0
plugin is activated, all other questions = no.
The site isn't public now (folder security), but I can give you access in pm.
Have a nice holiday!
Graag Inloggen deelnemen aan het gesprek.
- Ruud van Lent
- Offline
- Berichten: 1624
- Ontvangen bedankjes 107
back from vacation and picking up the slack
is the site live or still in development?
You can sent me details here in the forum in 'confidential' tags (the padlock button on the editor toolbar, or sent me an emial info [at] onlinecommunityhub [dot] nl
Graag Inloggen deelnemen aan het gesprek.
- Peter Klinke
- Onderwerp Auteur
- Offline
- Berichten: 9
- Ontvangen bedankjes 0
hope you had nice holiday.
The site is still in development.
There is still only one image in the office folder.
Graag Inloggen deelnemen aan het gesprek.
- Ruud van Lent
- Offline
- Berichten: 1624
- Ontvangen bedankjes 107
tried to login but get the (joomla) message:
"Login denied! Your account has either been blocked or you have not activated it yet."
Graag Inloggen deelnemen aan het gesprek.
- Peter Klinke
- Onderwerp Auteur
- Offline
- Berichten: 9
- Ontvangen bedankjes 0
Graag Inloggen deelnemen aan het gesprek.
- Ruud van Lent
- Offline
- Berichten: 1624
- Ontvangen bedankjes 107
Graag Inloggen deelnemen aan het gesprek.
- Peter Klinke
- Onderwerp Auteur
- Offline
- Berichten: 9
- Ontvangen bedankjes 0
Graag Inloggen deelnemen aan het gesprek.
- Ruud van Lent
- Offline
- Berichten: 1624
- Ontvangen bedankjes 107
as you can see the required 'src' that is required is not present, instead there is a data-src pointing to the image. So the module (or template) has javascript in place to read that data-src and then set that in the visitor browser as src > displaying the image.
This was (!) a common practise to enable lazyloading when that was not supported by browsers.
ochResponsiveImages runs on the server and not on the browser, so it doesn't see the img with a src attribute instead it sees an invalid image without the src attribute.
Maybe when you disable lazyloading on that template / module it will correctly set the image as src instead of as data-src. ochResponsive images will then pick it up and you can configure ochResponsiveImages as well to implement the lazy loading as that is currently supported by all browsers.
Does this make sense? can you give that a try?
Graag Inloggen deelnemen aan het gesprek.