Updating Fabrik via Extension Manager

[JackGoa]

Quick question. When updating Fabrik via the Extension Manager to 3.6, or 3.7, etc, do I still have to then also update from Github, or is that the latest from Github?

 

[JackGoa]

On two sites now, I ran the update via Extension Manager. Then the version the version shows as 3.7. I then unzip from Github, go to Discover and boom, back to 3.6?

This is using the Master zip from Github. Should I download the joomla37.zip instead?

 

[troester]

If you update via extension manager you don't need a GitHub update.

But GitHub is ok. At the moment it hasn't got the 3.7 tags yet, so it's showing the wrong version. But it's the latest code.

Anyway: Fabrik3.7.1 is coming soon.

 

[JackGoa]

Ok thanks.

 

[cheesegrits]

I just committed the 3.7 release updates / tag.

-- hugh

 

[JackGoa]

Ok, so with a major release like from 3.6.x to 3.7, use Extension Manager? All other times, download from Github?

 

[cheesegrits]

The only reason you sometimes need to run the installer through J! is to get any SQL updates run. Not every release has SQL updates. I usually recommend installing every new release through J!, just in case we have any SQL updates that need doing. Also to get your version number bumped up in J!'s schema table.

-- hugh

 

[JackGoa]

I have noticed that when a larger release comes out, the version number doesn't change unless updated through J!

Thanks for clearing that up!

 

[cheesegrits]

Yup, the version numbering is updated by the J! updater, so won't happen if you only do github.

-- hugh