maybe one in 50 times a button is instantiated:

<PRE>
      Error:       1925
    Message: Unknown member CLIENTVERSION.
       Code: 
    Program: useraction_cfichandler
    Line No:      11832
     Client: 199.116.173.196
Post Buffer: 
</PRE>
Exception Handled by: Pesprocess.Error()

Hi Tuvia,

If I understand correctly, this is from V 2.23.x, more than 1 year old… I recall this error used to occur, it does not occur in more recent versions however.

Could you upgrade your app to V 2.26.x? This would fix the problem right away

1 year is pretty recent. Upgrading means doing all projects which is a bigger undertaking, especially w/ testing. Is that only option?

As FoxInCloud follows SemVer, all 2.x versions are back compatible.

The latest release (2.26.0) is fully compatible with the version you use (2.23.*).

You can just do routine testing.

that is great. will advise

You cannot run an FiC 2.23.x app under 2.26. The foxincloud.js expects certain scripts, such as modernizr, that the 2.23 does not load. Therefore I did have to update all projects. However the good news is that so far the errors have not reoccured, so it seems fine, thank you.

of course there are evolutions, however you don't need to change your code from 2.23 to 2.26.

you just need to use xxxProd.update.prg to automatically update your application(s)

I wish life were that easy. I have never upgraded from one version of FiC to another without the need for adjustments. New in version 2.6 is the following error upon accessing the site:

This haS been verified in all android browsers. It has also been reported in multiple PC's, however since in development we do not see it in FF or IE we suspect Chrome, although it could be more than Chrome and we are not seeing it.

Customer is losing orders left and right, phone users have no idea what to do.

Pressing OK just repeats the messages. I found that if I refreshesd the browser twice, I got past the message.

So now the site is running but 2/3 of users are stymied.

I wish browsers would smartly load new files when updated instead of using their cache; that's why we have this message (not an error).

you can find JS quirks to force browser to reload all resources, difficult to test on all possible browsers…

your suggesteds quirk and implementation?

nothing really works except manually reloading the site (click the browser's reload icon)

this does not work: location.reload(true) (https://stackoverflow.com/questions/5721704/window-location-reload-with-clear-cache)

users can also clear the cache (in browser's options)

no miracle solution however

In that case you should remove that message, at the very least replace it with a message users can understand what action to take. Now they juat walk away, the message is not understandable, and the client just loses potential customers.

BTW, the message is also inaccurate - it appears ALWAYS on android browsers whether or not there is anything in the cache. Same with some Chrome browsers.

So Immesdiately, high priority:

1. message must be disabled. site is losing majority of customers, cannot roll back to 2.23, 2,26 fixed various bugs

In general:

1. Message is more often than not inaccurate there is nothing in the cache.
2. The message text does not explain what is happening so the user just leaves the site.
3. Optimum would be removing the message
4. Next best would be an configuration option to remove it
5. Next best would be different or configurable text

you can test without it:

modify command awServer

if Vartype(m.this.clientVersion) == 'O' and this.clientVersion.minorLT(m.Server.oSemVer) and .F. && add 'and .F.'

If you can/want to reword the message, please go ahead

will do asap and advise

Based on that code though, I do not know why it would always falsely claim to be outdated.

they'll get the msg as long as the browser has not reloaded FoxInCloud.js to a version that matches the server's version.

without reloading, the app won't work because of JS errors.

I get that, but people getting it who have never run a FiC anything and have never had a dfoxincloud.js before.

Tuvia, we are seeking a solution, not playing who will be right last…

User has to take an action to work around the cache: how to trigger and explain this action? You know your US-based users far better than us.

My point is not about right, my point is that features are always being added to FiC, and this is an example -- you cannot just recompile a project to a new version and off you go. You have to test it.

I do not know how an android user refreshes the browser, so I have android users that cannot get past the message. I will go look on an android phone. These are not very high level users -- they can barely use their phones. Therefore I think this is not a good solution to the problem.

If we wanted to display a message for [english] PC users, I would imagine it could be something simple like:

Please refresh your browser to access this site.

with no title on the messagebox. "Load new version" is very scary to unknowledgable users.

In 2.26.1-beta.6, we'll add a version in queryString to *.js and *.css URLs as explained here

eg. http://foxincloud.com/awScripts/FoxInCloud.js?2.26.1-beta.6

This should eliminate the problem.

If an issue remains, we'll add a sub-classable method to customize the message.

Sounds like a good plan.