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 Doesn't work with other Plugin

More
1 year 1 week ago #2764 by Helmut
Doesn't work with other Plugin was created by Helmut
This message contains secure information

Please Log in to join the conversation.

More
1 year 1 week ago #2765 by Ruud van Lent
Replied by Ruud van Lent on topic Doesn't work with other Plugin
Hi Helmut, thanks for reaching out.
just te be sure: what happens when you disable the responsiveimages plugin? is the image displying correctly? is the filename correct without it having prepended the direcoty / site name?

Is the site on a subdirectory? e.g. domain.com/abc where abc is the subdirectory?

As for 'issue 2 this is not an issue but is actually exactly how it should work: you create a directory, put in all images for the gallery and when pointed to it ochGlightox will take all files in that directory and display them in a gallery.
ochGlightbox has no knowledge of the images other then they are there: show them.

I have ochResponsiveImages which also creates webp images but it does so in a separate 'cache' directory specifically for this reason: never change the contents of a directory that you (the responsiveimages) plugin do NOT have control over and is not yours to change as that might (and if it might it will as you can see) change the sites behavior. That and also when cleaning up these converted images: they are all over the place and cannot be removed easily without going through every directory that has images.

So this is a consequence (probably not foreseen) of a choice made by the plugin developer: this is not only an issue qith ochGlightbox but with every plugin that uses the contents of a directory.

in ochResponsiveImages I have added an option to exclude certain directory from being handled, may that is also possible for the free plugin?

Or you do not use the ochGlightbox tag pointing to a directory bu use the ochGlightbox where you can upload / select every image manually (not ideal but maybe that is an option).

Best is probably to reach out to the developer of the free plugin and point out to him that the location where he is placing the webimages is causing issues for other extensions / templates

Please Log in to join the conversation.

More
1 year 1 week ago - 1 year 1 week ago #2767 by Helmut
Replied by Helmut on topic Doesn't work with other Plugin

Hi Helmut, thanks for reaching out.
just te be sure: what happens when you disable the responsiveimages plugin? is the image displying correctly? is the filename correct without it having prepended the direcoty / site name?

> When i disable the plugin, the path to the image is correct

Is the site on a subdirectory? e.g. domain.com/abc where abc is the subdirectory?

> Yes, the site is for the moment on a subdirectory. The subdirectory is testsite4
For the moment, i add my base-url to the <img src=...> in an override of gallery_masonry.php. This workaround helped to show the images in the frontend.

As for 'issue 2 this is not an issue but is actually exactly how it should work: you create a directory, put in all images for the gallery and when pointed to it ochGlightox will take all files in that directory and display them in a gallery.
ochGlightbox has no knowledge of the images other then they are there: show them.

I have ochResponsiveImages which also creates webp images but it does so in a separate 'cache' directory specifically for this reason: never change the contents of a directory that you (the responsiveimages) plugin do NOT have control over and is not yours to change as that might (and if it might it will as you can see) change the sites behavior. That and also when cleaning up these converted images: they are all over the place and cannot be removed easily without going through every directory that has images.

So this is a consequence (probably not foreseen) of a choice made by the plugin developer: this is not only an issue qith ochGlightbox but with every plugin that uses the contents of a directory.

in ochResponsiveImages I have added an option to exclude certain directory from being handled, may that is also possible for the free plugin?

> That was i big mistake of mine - sorry for that. The free plugin doesn't store images here. The webp images were created by another plugin in the past. After i deleted the webp images, it worked!!! 


Or you do not use the ochGlightbox tag pointing to a directory bu use the ochGlightbox where you can upload / select every image manually (not ideal but maybe that is an option).

> I've tried this and load the images manually in the editor but can't get the masonry gallery work without the parameter. Is it possible to get it work?

Best is probably to reach out to the developer of the free plugin and point out to him that the location where he is placing the webimages is causing issues for other extensions / templates

 

Last edit: 1 year 1 week ago by Helmut.

Please Log in to join the conversation.

More
1 year 1 week ago - 1 year 1 week ago #2771 by Ruud van Lent
Replied by Ruud van Lent on topic Doesn't work with other Plugin
Hi,
so as I suspected: the issue here is in the responsiveimages plugin that doesn't correctly handle sites that are on a subdirectory: that is a bug.
Likely when you put that site to the root (when going to production) this issue will be gone. The developer should be able to fix that as it is a valid use case for sites and should working correct.

I see I omitted the 'module' in my advice: you can create a ochGlightBox MODULE where you can upload all the images and configure that to display with e.g. masonry. The module can then be placed anywhere in your content with the tag{ loadmodule ...} or you can display it on any template position.
Last edit: 1 year 1 week ago by Ruud van Lent.
The following user(s) said Thank You: Helmut

Please Log in to join the conversation.