Confirm n 6.10.3 with my skin. I get a 404 if I try and preview on any status (Draft, Members, Public)

EDIT
Tried bootstrap and forums and no change ?? Maybe some weird setting I have ???

I confirm there is a bug. We'll try to fix this today.

Fixed in commit https://github.com/b2evolution/b2evolution/commit/02bf43c526a5eb397d05fd7c552aea3ce2ede1d2.

@yurabakhtin wrote earlier:

Fixed in commit https://github.com/b2evolution/b2evolution/commit/02bf43c526a5eb397d05fd7c552aea3ce2ede1d2.

@yurabakhtin works fine! Thanks for the fix!

Just a note for anyone who wants to modify the files as in
https://github.com/b2evolution/b2evolution/commit/02bf43c526a5eb397d05fd7c552aea3ce2ede1d2

In my version (6.10.3) of [/conf/_application.php] line 24
is $app_date = '2018-09-27';
not $app_date = '2018-10-17'; as shown in the fix

All fixed

Thanks

@amoun Yes, you are right, just ignore my modification in the file conf/_application.php if you do manual changes in your current release. We change the $app_date for next release. You should update the config variable only when some css or js files were changed in order to update your browser cache.

@yurabakhtin - ok. let's wait to the next release. But have also a look at this:

@yurabakhtin wrote earlier:

@amoun Yes, you are right, just ignore my modification in the file conf/_application.php if you do manual changes in your current release. We change the $app_date for next release. You should update the config variable only when some css or js files were changed in order to update your browser cache.

Thanks for that. I was wondering why the date needed changing, however I have Firefox delete the cache each times it closes, so it should never impact in that way. Of course now I've just though about what I've said, other users probably won't have their cache deleted each instance :()

@saunders

Oh! the date I've changed it to [$app_date = '2018-10-02';] in line with the release and the warning goes away :)

So the date has it''s uses

UPDATE
Mind you, why a future date should trigger the warning. Just checked that 2018-10-01 doesn't but anything before that does as does 2018-10-04

@amoun wrote earlier:

Just a note for anyone who wants to modify the files as in
https://github.com/b2evolution/b2evolution/commit/02bf43c526a5eb397d05fd7c552aea3ce2ede1d2

In my version (6.10.3) of [/conf/_application.php] line 24
is $app_date = '2018-09-27';
not $app_date = '2018-10-17'; as shown in the fix

All fixed

Thanks

It was first released on September 27th but we re-released

So question :: if my install is the Sept 27 what are the changes in the Oct 2nd, as I have to download and upload over a 500kb connection, being unable to auto update. I'd rather do a few bug fixes.

@saunders wrote earlier:

@yurabakhtin - ok. let's wait to the next release. But have also a look at this:

If you don't want to see that red error message you should revert $app_date to '2018-10-02', but it doesn't matter fro correct system work, it's just info data.
Sorry for this confusion with app data, I will not touch that var for similar quick bugfixes in future.

@amoun wrote earlier:

So question :: if my install is the Sept 27 what are the changes in the Oct 2nd, as I have to download and upload over a 500kb connection, being unable to auto update. I'd rather do a few bug fixes.

I think you should check this compare page https://github.com/b2evolution/b2evolution/compare/88e38f61bc87b07011fdb2975ff02b5dceeaa401...6.10.3

@yurabakhtin wrote earlier:

@amoun wrote earlier:

So question :: if my install is the Sept 27 what are the changes in the Oct 2nd, as I have to download and upload over a 500kb connection, being unable to auto update. I'd rather do a few bug fixes.

I think you should check this compare page https://github.com/b2evolution/b2evolution/compare/88e38f61bc87b07011fdb2975ff02b5dceeaa401...6.10.3

Thanks: I'll apply the bits

Beautiful! Thanks, Saunders, for getting this started. You just saved me a ton of time!

The fix will be part of b2evo 6.10.4.