Hello Denis, one question. Many people have the same problem ("failed to open stream") because (i think) your update need allow_url_fopen, but this is not secure.

Why do you use cURL for aceSEF? Then many peoples with the same server configuration like me have no problems to update and you need only an few code lines to realised it with aceSEF.

I would be delighted if you were to think about this!

Greetings from Germany!

Hello Denis, one question. Many people have the same problem ("failed to open stream") because (i think) your update need allow_url_fopen, but this is not secure.

Why do you use cURL for aceSEF? Then many peoples with the same server configuration like me have no problems to update and you need only an few code lines to realised it with aceSEF.

I would be delighted if you were to think about this!

Greetings from Germany!

In fact, since AceSEF 1.2.4 I use 3 methods (cURL, fsockpen, fopen) to check the version but just now I realized that the function "JInstallerHelper::downloadPackage" (a Joomla! Framework function) that I use to download the file from joomace.net uses just fopen.

I'll check this issue asap.

That are good news! Many user will be pleased! Me too

Hello Denis, is this problem fixed in version 1.3.2 ???

1.3.2 ??? The latest version is 1.3.1 but it'll be fixed in the next version.

Denis Dulici wrote:
1.3.2 ??? The latest version is 1.3.1 but it'll be fixed in the next version.

Yes the last is 1.3.1 and the next 1.3.2 or not

I mean the next Version!

Thanks...

The next is 1.5

Well, I have 1.3.2 and have this issue.
I cannot upgrade via downloadID.

So should I upgrade manually?

So should I upgrade manually?

YES, we waiting for Version 1.5. It comes in 2 weeks (we hope)

Greetings!