tried that, did not work for me - had to download and update each single one of them manually ...

I always find the update process hit and miss. 

Some things do update, some don't.  . 

Currently, not a lot of joy

Updater is v1.3.4

:D very well said! It is by no means reproducable what happens when you hit the update button.

Hello,

Did you add your domain(s) to your SEBLOD-Account (Member Account > My Domains)?
And did you enter the secret key to your domain (Member Account > Edit Profile)?

Greetings
Skepsis

Thanks. Yes I did that, no change. 

Anyway it raises the question why they need to know my domains? What are they going to do with that? Puts the project in a dodgy light in times every company and government is spying on clients and citizens.

Hi

No joy for me either.

How have you entered your your localhost sites?

I have done like this: localhost:8888/[site-name]

Localhost unfortunately does not work in any form, problem is that is treated the same as other domains that can be registered only once and is already registered to somebody else.

My issue was a non-issue

1

didn't know local host couldn't be used and

2

did not realise difference between subscription options   ...

Hello,

We are not looking to highlight your domains or sites to anyone.

Here, the purpose is only to (try to) control who is allowed to download our paid plug-ins. And this is not only for us, but also for any person/company which choose to pay for using a special/specific product. We try to be fair with our customers, and in the meantimes to exclude the ones who don't want to follow the rules...

We understand that the use of the updater may be complex sometimes or for some people or specific contexts, but that is for now the solution that we provide in order not to update manually (and when everything is set up correctly, I can assure you that it works like a charm). It may be improved (or more bulletproof) in the future but as you know there are also a lot of other things to improve and/or to implement.

But in order to make it easy, the important change that we are going to make (as soon as we can) on SEBLOD.com, is to open the download of ALL free products. It means that you won't need to authenticate and add-to-cart free products anymore, and so... you'll also be able to upgrade all free products from the Joomla! Extension manager (i.e without the use of the updater add-on). The updater will only be required for paid products.

That's the one step forward we can do for now on this topic. Hopefully you'll find it useful.

Saba. 

Hello. I have the same issue here. I can not update  SOME Seblod plugins after SEBLOD  3.11.3 update

I updated successfully just  one:

- SEBLOD Iporter Add-on

and I am not able to update these plugins:

- SEBLOD Exporter Add-on
- SEBLOD Form & List Pack
- Address to Coordinates Field Plug-in for SEBLOD
- Search Query Field Plug-in for SEBLOD

I get the same errors mantioned above

Warning

Update path does not exist.

Message

Error updating COM_INSTALLER_TYPE_TYPE_.

Error

An error has occurred.

- The domain www.forum-media.cz is properlly added to my SEBLOD-Account 

- The secret key is well copied.

- I manually unistalled and re-installed the SEBLOD UPDATER with no luck.

Can you please advice what else should I check? It is a big website for important client.

Thanks so much

Michal

Hello,

It seems that you have successfully updated on June 22th.
Please note that you can use the updater only once per product version per domain. So each site should have their own domain name.

A new version of the updater add-on has been published ... in order to display the "requirements" before update directly from the back-end.

Saba

How can you mark a topic "solved" when so many people still report issues? That includes me even after taking care again and again and again of the secret key and added domains - live update just does not work. I still get the same error I reported in first post. Sorry but this is just annoying ... even paid extensions have to be updated manually.

SEBLOD Updater 1.3.5 to 1.3.6 > I get the same error I reported in first post. 

Is this yet reported to GitHub ?