It is one point ten like it says in the post..


One point nine point four point three was the last one and now it is one point ten not one point one, 9 + 1 = 10...

Sorry you think it is a mistake...

_________________
Extensions » Modules/Tags click the name of the module/tag or Help to the right to get its parameters.
Right click and view source is a great way to see what you have to work with.
Check ver. CMSMS, PHP, server OS, in System Information page.
Default content http://multiintech.com/defaultcontent/
Ever wonder what happened to the Album module? Well it is alive and well.
http://album.multiintech.com/

Yeah, OK... I know it but still... this is strange.
When you look at the number from the mathematical point of view, it's not really "there".

I know you want:
1.9.1
1.9.2... etc.
then
1.10
but you normally erase the zero and you have 1.1
which is lower than 1.9.

I've never seen in any script such naming. This is what I call a mistake. OK, not really a total mistake but when it comes to script numbering it's like something different, something which might be misleading. For me - a mistake. A mistake in marketing the script, too. I love CMS MS too much not to shout it out.

EDIT not to add multiple posts:
uniqu3 yeah, but still... I'd rather see 1.9.5+ than 1.10...

True but naming 1.10 to 2.0 would also be wrong especially when there was announcement about 2.0 being shelved not so long ago.

_________________
CMSMS Blog - I do this!
Forge profile
Github profile
Twitter
=============================================
Support CMSMS

Is the number really that important?

_________________
Make your community a better place!

It's imposible to look at a version number from a mathematical point of view, that would make a version number like 1.9.4 invalid because it has two dots in it.
Also, a lot of software uses this kind of version numbers. For example: Firefox, Opera, Ubuntu, Joomla! and probably many others. It's very common.

Having said that, I also think the changes in 1.10 are big enough to give it a new major version number (2.0). The only thing is that it might be a bit confusing with the "old" 2.0 project.

In other words, let's keep this discussion for what it is.

_________________
Make your community a better place!

thank you guys. love the lightweight microtiny but i am really missing file uploading function (file manager) in it.

I can't believe I've just read through numerous posts about version numbers. Do we have nothing better to do?

Why not start using roman numerals: I.X

Some people can't seem to count to 10 using decimals, you expect them to know roman numerals

_________________
Follow me on twitter
--
if you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
----------------
Don't make me angry..... you won't like me when I'm angry....

I wont go in a discussion about version-numbers, but as far as trimming of zeros is involved, I only know of that as LEADING zeros. So 01 and 001 might be written as 1.
Trailing zeros are never trimmed, as 10, 100 is not the same as 1.

Ronny

Use binary ..... 0001.1010

Why is Calguy's posts always duplicated 2 or 3 times? It's a good way to make sure that we get the message

c'omon!
Each number group is in versioning handled separate starting from left.
The dot is the group delimiter - not a desimal sign

_________________
ReneH
A search will save you hours waiting for an answer! http://www.f150online.com/forums/member ... search.gif

Would it be within the realm of possibilities that we stop arguing about version numbers and focus on the real purpose of this forum?

The dev team deserves a lot of praise, gratitude and support for all the voluntary (that means "unpaid") hours they've devoted to making CMSMS more powerful, flexible and easier to use for ALL of us. They most definitely do NOT need to read nor should they have to respond to completely irrelevant posts like the far too many comments above.

i upgraded another more complex cmsms website. first i upgraded all modules and the cms to cmsms 1.9.4.3 and then copied the new 1.10 files and ran upgrade.php. everything went fine. but when i open a page in backend and want to save it, i get:

even when the template just contains "{content}".
what i am doing wrong??

edit: i mentioned nusoap was still installed even when i hit "uninstall". now i removed it manually on ftp
----------------------------------------------

Cms Version: 1.10

Installed Modules:

CMSMailer: 2.0.2
FileManager: 1.2.0
ModuleManager: 1.5
News: 2.12.2
Printing: 1.1.2
Search: 1.7
ThemeManager: 1.1.4
TinyMCE: 2.9.4
CGExtensions: 1.27.1
CGSimpleSmarty: 1.4.10
CGEcommerceBase: 1.3.5
CGPaymentGatewayBase: 1.0.11
FrontEndUsers: 1.16.2
Products: 2.15
Orders: 1.13
Cart: 1.8.1
PaypalGateway: 2.3.5
SelfRegistration: 1.6.13
MenuManager: 1.7.6
CustomContent: 1.7.3
Promotions: 1.0.14
Captcha: 0.4.5
Gallery: 1.4.4
CMSForms: 0.0.24
Twitter: 1.10
JQueryTools: 1.0.10
AdvancedContent: 0.9
CGUserDirectory: 1.2.6
TemplateExternalizer: 1.3.1
FormBuilder: 0.7
FormBrowser: 0.4
SameCountryTax: 1.1
CMSPrinting: 1.0
MicroTiny: 1.1


Config Information:

php_memory_limit:
process_whole_template: false
output_compression: false
max_upload_size: 200000000
default_upload_permission: 664
url_rewriting: mod_rewrite
page_extension: .html
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale: en_US:UTF8
default_encoding: utf-8
admin_encoding: utf-8
set_names: true


Php Information:

phpversion: 5.3.6-nmm1
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 64M
max_execution_time: 60
output_buffering: On
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 200M
upload_max_filesize: 200M
session_save_path: /tmp (0333)
session_use_cookies: On (True)
xml_function: On (True)


Server Information:

Server Api: cgi-fcgi
Server Db Type: MySQL (mysql)
Server Db Version: 5.1.43


----------------------------------------------

damn it. solved! had an incompatible udt which was set in eventmanager contenteditpre!