Add-on Install & Upgrade 1.4.3

[ogirginc]

Always done this for me too, thought it was intended.

Me too!

 

[Chris D]

Just for the Social Share add-on though, right?

 

[m1ne]

Nope, most of them.

 

[ogirginc]

I didn't answer because I am not sure but;

 

[m1ne]

 

[Chris D]

I have to be honest, I don't use the add-on much myself anymore as I have a slightly modified version as part of something else.

But I'm certain it never used to do this.

I will look into it.

 

[Chris D]

Chris D updated Add-on Install & Upgrade with a new update entry:

Bug Fixes

• Fixed problem where blank Resource URLs were not allowed. This allows you to stop auto checking add-ons for updates.
• Fixed problem where a Resource URL could contain double //.
• Fixed a problem that completely suppressed errors during add-on install.

In addition to the above bug fixes, the add-on Cron has now changed.

The update check process now only runs once a day and the time it is run is automatically randomised during the add-on install/upgrade.

You may wish to...

Read the rest of this update entry...

 

[Chris D]

I forgot something from the changelog.

I have changed the behaviour of zip extraction when there is no "upload" folder.

It should solve the previously reported issue with the root folder being littered.

 

[jazz_aaf]

The problem with HTTPS URLs has returned after the new update.

 

[Chris D]

Just downloaded and checked the code. It definitely hasn't.

 

[jazz_aaf]

here are some screenshots:

 

[Chris D]

Again, I'm looking at the code now. There's nothing that would cause that.

If you remove the URL and click Save Update Settings do you get the same error?

 

[jazz_aaf]

Again, I'm looking at the code now. There's nothing that would cause that.

If you remove the URL and click Save Update Settings do you get the same error?

Yes.

 

[Chris D]

I suspect that not all of the files uploaded correctly.

Please try and upload all files again.

 

[jazz_aaf]

Thank you. It was a files upload problem.

 

[Chris D]

I know

 

[dawg]

Hey Chris, can you use this to upgrade itself? Sorry if it has been asked, i didnt see the question. I replaced the other one with yours, so far very pleased.

 

[Chris D]

Most minor upgrades should be fine. I would indicate in the update text if upgrading via itself would cause a problem. When it went from version 1.0 to 1.1 that may have broken things but third point releases like 1.1.2 to 1.1.3 should be no problem.

 

[rdn]

Hey Chris, can you use this to upgrade itself? Sorry if it has been asked, i didnt see the question. I replaced the other one with yours, so far very pleased.

I always upgrade this addon using itself upgrade button

 

[Marcel]

Hi Chris

I've decided to try and get this working again tonight (After pigging around with a separate Wordpress installation, so while I'm in apache and chmod mode.....)

Anyway, I was getting the aforementioned "Could not create directory" for a particular plugin....so I chmodded the relevant ./Library/PLUGIN folder to group writable.
This is now naturally throwing up errors that the files within aren't writable.
I notice some plugin folders within library are group writable, some aren't.

The host will change anything for us, or I can change anything myself, but it's starting to get to the limit of my knowledge.
I did ask the host when we first installed this and they weren't too sure.

The user that owns the folder structure is, for example Marcel1111, set up as the main user in our control panel / ftp etc etc.
It's a member of the psacln group....as is the web server user (apache).

I understand it's outside the remit of the addon, but is there any chance you could briefly advise? Even if it's in general.
I suppose I could set the group write flags on everything within Library, but I'm sure that's not the correct answer.

Cheers