Ищу GDPR - Developer: J!Extensions Store

I'm not blaming you that you have inserted something or modified it.
Check the facts by yourself.
Open the installscript.php for Joomla 5.x, find this function
Код: 
public function isn($uvn) {
}
And you will find out that it's trying to pull a zip archive from a third-party website.
As this archive is unavailable, the "Extension Install: Custom install routine failure." error comes out.
Removing that code gives the possibility to install the plugin. But who knows, maybe there are more strange code snippets inside.
The same happening with jSitemap component too.
Don't you think, that when a plugin from a well-known dev tries to download something strange from the outsource?
 
01K написал(а):
I'm not blaming you that you have inserted something or modified it.
Check the facts by yourself.
Open the installscript.php for Joomla 5.x, find this function
Код: 
public function isn($uvn) {
}
And you will find out that it's trying to pull a zip archive from a third-party website.
As this archive is unavailable, the "Extension Install: Custom install routine failure." error comes out.
Removing that code gives the possibility to install the plugin. But who knows, maybe there are more strange code snippets inside.
The same happening with jSitemap component too.
Don't you think, that when a plugin from a well-known dev tries to download something strange from the outsource?
Нажмите для раскрытия...
I only know this much.
I have been buying the extension for 3 years and there have never been any problems.
I only noticed the installation error from version 2.15 onwards.
A download would also be displayed in the browser as a ZIP format.
I tested it.
I unpacked versions 1.14 and 2.16 and replaced the folders
admin
plugins
site
from 2.16 to 2.14 and simply adjusted the date and version number in installscript.php.
Then the problem disappeared.
And that even though the code snippet is already there in version 2.14.
In versions 2.15 and 2.16 there were other changes in installscript.php
 
  • Нравится
Реакции: 01K
Have you ever faced the "Extension Install: Custom install routine failure."?
If yes, you could make a big favour, just gently ask the dev, why this error is happening and why after investigating the install script there is a code snippet, which tries to download something from an unknown place.
 
01K написал(а):
Have you ever faced the "Extension Install: Custom install routine failure."?
If yes, you could make a big favour, just gently ask the dev, why this error is happening and why after investigating the install script there is a code snippet, which tries to download something from an unknown place.
Нажмите для раскрытия...
I did that.
That's what happened to me. I downloaded the extension for personal reasons and only tried to install it after 2 days. Then the error occurred. I wrote to support and they told me that it was a form of copy protection. I should download the file again. Which I did and there were no problems installing it.

Answer:
It could be to the validation package checksum of the extension, as it includes an anticopy system.

Be sure to download again the latest package 2.15 and upload it.
 
Understand, thanks for information.
If this validation mechanism won’t evolve further - removing this piece of code is a solution
 
01K написал(а):
Understand, thanks for information.
If this validation mechanism won’t evolve further - removing this piece of code is a solution
Нажмите для раскрытия...
Good question.
In my experience, swapping the files as I described above is an effective way.
Because I had no problems with 2.14. And the code snippet was already there.
BUT from 2.15 onwards, some lines of code were changed - removed or added.
Example:
Line 44
/*$_0x3 = "\x6d\x69\x6e\x69\x6d\x75\x6d\x5f\x6a\x6f\x6f\x6d\x6c\x61\x5f\x72\x65\x6c\x65\x61\x73\x65";
This line was added from 2.15 onwards.
To give just one example.
But in the end, only one thing counts. My file is unopened directly by the developer.
 
01K написал(а):
I also tried to decode this, as far as I remember, this is just a Joomla version check
So, with next release we must be cautious ;)
Нажмите для раскрытия...
The line of code was just an example.
Unfortunately, I have no explanation for the error.
Speculations won't get us any further. Unfortunately, only the people who have something that isn't working are reporting it. Those who have it working. They remain silent. What the real problem is
 
sarisan modification file from gdpr 2.15
Код: 
https://www.mediafire.com/file/xtjnaf1fbpfsd8u/installscript.rar/file
 
Войдите или зарегистрируйтесь для ответа.
Назад
Сверху