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 About the configuration options
- Roussel Grégory
- Onderwerp Auteur
- Offline
Minder
Meer
- Berichten: 24
- Ontvangen bedankjes 1
9 maanden 1 week geleden #2769
door Roussel Grégory
About the configuration options werd gestart door Roussel Grégory
Hi,
first of all it works fine.
But as there's no tooltip informations on each option of the plugin, I wonder what exactly doing the "Enable HTML cleanup" ?
Thanks
first of all it works fine.
But as there's no tooltip informations on each option of the plugin, I wonder what exactly doing the "Enable HTML cleanup" ?
Thanks
Graag Inloggen deelnemen aan het gesprek.
- Ruud van Lent
- Offline
Minder
Meer
- Berichten: 1624
- Ontvangen bedankjes 107
9 maanden 1 week geleden #2770
door Ruud van Lent
Beantwoord door Ruud van Lent in topic About the configuration options
Hi,
that is an 'old' setting that is not removed because I do not want to break things for people who are using it.
Basically there are two ways of searching for an element in HTML: via the DOM or via a regex.
Doing this via the DOM is the easiest as it just lists all the <img> elements it finds, doing it via a regex is error prone as you then need to construct a regex (search): an image can be set as <img src="...." > but could also be <img alt="..." src="..."/> and al kind of combinations of "/ ' ending in > or />, etc.
So there is a chance of the regex failing to find and extract the correct information.
That is why I initially thought it was 'brilliant' to use the DOM for finding and replacing the <img> elements....
Until I learned that HTML is 'forgiving' when there are errors in the HTML document: the browser still tries to display the page as best as possible if there are errors: this is a 'good' thing, but not for querying the DOM as that requires correct HTML as otherwise it will give an error.
What I learned is that there are a lot of Joomla sites / templates out there that really mess up the HTML: it displays okay but it is full of error and that results in ochResponsiveImages to NOT find all the images... So I thought let's first read the HTML and use the DOM to save it and by doing that produce cleanup HTML.... As it turned out, that in some cases didn't work and mangled badly formatted sites...
So I just implemented regex as second (and now preferred) way to find the images... The cleanup HTML option is still there but should not be used.
So long story short: I tried to fix broken and poorly developed sites and that back-fired This toggle is still in there for legacy purposes but will eventually be hidden and after that removed from the code.
that is an 'old' setting that is not removed because I do not want to break things for people who are using it.
Basically there are two ways of searching for an element in HTML: via the DOM or via a regex.
- DOM: The Document Object Model (DOM) is a programming API for HTML and XML documents. It defines the logical structure of documents and the way a document is accessed and manipulated.
- Regex: Regular Expressions, commonly known as "regex" or "RegExp", are a specially formatted text strings used to find patterns in text. Regular expressions are one of the most powerful tools available today for effective and efficient text processing and manipulations.
Doing this via the DOM is the easiest as it just lists all the <img> elements it finds, doing it via a regex is error prone as you then need to construct a regex (search): an image can be set as <img src="...." > but could also be <img alt="..." src="..."/> and al kind of combinations of "/ ' ending in > or />, etc.
So there is a chance of the regex failing to find and extract the correct information.
That is why I initially thought it was 'brilliant' to use the DOM for finding and replacing the <img> elements....
Until I learned that HTML is 'forgiving' when there are errors in the HTML document: the browser still tries to display the page as best as possible if there are errors: this is a 'good' thing, but not for querying the DOM as that requires correct HTML as otherwise it will give an error.
What I learned is that there are a lot of Joomla sites / templates out there that really mess up the HTML: it displays okay but it is full of error and that results in ochResponsiveImages to NOT find all the images... So I thought let's first read the HTML and use the DOM to save it and by doing that produce cleanup HTML.... As it turned out, that in some cases didn't work and mangled badly formatted sites...
So I just implemented regex as second (and now preferred) way to find the images... The cleanup HTML option is still there but should not be used.
So long story short: I tried to fix broken and poorly developed sites and that back-fired This toggle is still in there for legacy purposes but will eventually be hidden and after that removed from the code.
De volgende gebruiker (s) zei dank u: Roussel Grégory
Graag Inloggen deelnemen aan het gesprek.
- Roussel Grégory
- Onderwerp Auteur
- Offline
Minder
Meer
- Berichten: 24
- Ontvangen bedankjes 1
9 maanden 1 week geleden #2772
door Roussel Grégory
Beantwoord door Roussel Grégory in topic About the configuration options
Thanks a lot for this complete and useful explanation
Graag Inloggen deelnemen aan het gesprek.