Check Versions of Plugins

YouTube · Post by **Jane** » 18 May 2012 21:27

I think they were caused by data problems in the 'Store', I have re-uploaded mine and they seem to match.

A good double check is the view source on the Store and check the version on that.

BillH · Post by **BillH** » 19 May 2012 01:58

Jane,

The four I was having problems with before are OK now, but Find Date Phrases is having the same problem.

Bill

johnmorrisoniom · Post by **johnmorrisoniom** » 19 May 2012 07:45

All Mine OK except 'Find Date Phrases'

'B. Upgraded' '0' '1.1' 'Find Date Phrases.fh_lua'

This is still showing same as before.

I went to plugin store and manually downloaded the current version of the plugin.

It would not run and install at first, I had to tell windows 7 to run it with FH.

Ran you plugin after the manual install. Same result.

Plugin reports my installed version as version 0 and updates it to 1.1.

I think this was also one of the very earliest plugins

YouTube · Post by **Jane** » 19 May 2012 09:37

Ok, I think Find Date Phrases is fixed now.

johnmorrisoniom · Post by **johnmorrisoniom** » 19 May 2012 10:15

Thanks Jane,
Date phrases now correctly reports version 1.1

Post by **tatewise** » 19 May 2012 13:00

What all the above highlights is a need for better Plugin management in both FH and the Plugin Store.
e.g.
In FH the Plugins window lists Plugins by Filename, and in the Details below, lists @Title:, @Author:, @Version:, @Last Updated: & @Description: from the script header.

In the Plugin Store the user can record a completely different Plug In Title, Author, Version & Description, and Updated is automatically set to the date of approval.

In my opinion the Filename, @Title: in header, and Plug In Title should all be the same, probably best to use ONLY use the Filename.
Likewise there should only be one Version set by the @Version: in header.

In FH the Plugins window should list a similar Status and Store Version as this Plugin currently provides in its Result Set.

Post by **tatewise** » 19 May 2012 13:50

I have an illustration of the above Plugin (mis-)management problems.

In FH the Plugins window lists Search and Replace Text with a Title below of Search and Replace and Version 1.2.

The Check Versions of Plugins strangely reports this as Not In Store, so does NOT offer to Upgrade it.

The Plugin Store does list a Search and Replace Text plugin with Version 1.4.
However, its Filename is Search and Replace1 which does not meet the Check Versions of Plugins search criteria.

Having downloaded Search and Replace Text plugin with Version 1.4 it is listed as Search and Replace.
The trailing Filename digit 1 has vanished.

BillH · Post by **BillH** » 19 May 2012 13:51

Jane,

All working fine for me now. All plugins updated and reported correctly.

Thanks!

Bill

YouTube · Post by **Jane** » 19 May 2012 18:47

Mike,
When files are uploaded to the store, if there is already an existing file (eg a new version is posted, it will add a number to the end. It's removed when the file is pushed for download and my plug in back end should be doing the same so trailing numbers and underlines should not matter.

The plugin uses the filename on your computer to check the plugin store. it does not use the title or any other field.

Post by **tatewise** » 19 May 2012 19:34

You have overlooked the point about the report of Not In Store when it is in the Plugin Store, but key Details have changed.

The Search and Replace Text V1.2 was downloaded from the Plugin Store some time ago with filename Search and Replace Text.

In the meantime the Filename has changed to just Search and Replace, although its Plug In Title in the Plugin Store is still Search and Replace Text.

I now have both Search and Replace Text V1.2 and Search and Replace V1.4 listed in FH.
Whereas, the Plugin Store only lists Search and Replace Text V1.4.

Without appropriate management, the Plugin Store will continue to allow Filename, @Title:, and Plug In Title to be different from each other.
Not only that, it allows them to be different in each Plugin Version.
This can only lead to further confusion.

YouTube · Post by **Jane** » 19 May 2012 19:48

I will update the name of the plugin when I get a chance, but that plug in was added very early in the beta, so my guess this the core of the problem. As far as I can see the file name been search and replace since January, it was search and replace text back in June 2011.

So I suspect you will not be happy which ever way I fix it.

Post by **tatewise** » 19 May 2012 20:47

Perhaps these comments are in the wrong Forum, and I should report them directly to Calico Pie Support.
The point I am making is not about your Plugins, but about the three different ways FH/Plugin Store entitle a Plugin.
Namely Filename, @Title:, and Plug In Title that can all be different, and altered in each Version.
Maybe Filename is the most important of these three, but does not even appear in the Plugin Store.

Until this is resolved it will continue to be a weak point.
There is little you can do to fix it.

YouTube · Post by **Jane** » 20 May 2012 09:00

Yes, but all three fields are in the control of the submitter, which was me.

So I need to go in and change them. The only thing Calico need to do is double check on submissions all three are the same. As far as I can see the issue only effects the older plugins and a couple of mine, which I will fix as I re-visit them.

Family Historian User Group