phpwcms_version variable

Use GitHub to post feature requests for phpwcms.
Locked
jmeyknecht
Posts: 112
Joined: Sun 11. Jan 2004, 23:13
Location: Merseburg, Germany
Contact:

phpwcms_version variable

Post by jmeyknecht »

hi, i was looking in the forum if there is still a existing variable like $phpwcms_version or something like that. but i did not find anything like this.

is there still a variable like this?

If you have several (multiple) instances of phpwcms running on one server, it would be cool to know which version (with updates and patches) you are running on when you login into the backend.

Maybe I'm blind and haven't found it yet. Would be cool if you could tell me if there is something existing like that yet.

If not, why not integrating? shouldn't be so difficult i think and i think it's very usefull.

cheers
cguenther
Posts: 111
Joined: Sun 11. Jan 2004, 12:41
Location: Halle, Germany
Contact:

Post by cguenther »

would be good to have that.

i would include that variable into include/inc_conf/conf.inc.php and name it $phpwcms["version"] to fit the variable namings Oliver already did.

By including in that file it could be easy accessable for later useage, e.g. for update-script or so.

greetings
jmeyknecht
Posts: 112
Joined: Sun 11. Jan 2004, 23:13
Location: Merseburg, Germany
Contact:

Post by jmeyknecht »

hmmm. then conf.inc.php must be writable :-( or you have to change it by hand.

must be in other file that is changed everytime an update or patch is delivered.

think Olliver knows file hierarchy best, maybe he has an idea or anyone else...

what do other users think about that variable?
mdgroot
Posts: 155
Joined: Wed 11. Feb 2004, 17:47
Location: Netherlands

Post by mdgroot »

I agree with the need of this (simple) variable.
It is a good way to determine what versions you have installed, what patches e.g.

especially if you have more sites to maintain ...
ionrock
Posts: 279
Joined: Fri 20. Feb 2004, 17:04

Post by ionrock »

in the phpwcms.php fie there is a variable called phpwcms["version"]. You could move this to the conf.inc.php I suppose since it all part of the same array. I hope that helps
jmeyknecht
Posts: 112
Joined: Sun 11. Jan 2004, 23:13
Location: Merseburg, Germany
Contact:

Post by jmeyknecht »

yoh, but this variable contains for example "1.1-RC2"

So you don't know which patch you already installed and which not.
ok, you could collect all cangelog-files and then you know.

I know, with little work, I can obtain the information, which patches i have installed, and so on.

But what I'm dreaming of, is a variable or function, that tells me really what version (with updates and patches) i have installed.

I saw, that the changelog files now moved into an seperate folder. One solution could be just to read the files from the folder and sort it by date and then list the newest, or something like that.
or maybe to read the whole folder and list an installing history. but so you could read in the backend what you have installed, with no click (or just one), without looking in the filesystem on the server.

As i said, no problem when you are just running on one phpwcms installation. but when you are running with multiple, then it is good to know which specific version you are running. (it's easier and faster)

and, don't forget... it's just a feature request ;-) (but i think a good one) :-))
ionrock
Posts: 279
Joined: Fri 20. Feb 2004, 17:04

Post by ionrock »

I see what you are saying now. I am working on a plugin framework that will register plugins and most likely it could handle patches as well so this could be a part of that very easily. If you have any ideas or thoughts on other aspects to managing a lot of different phpwcms site with different plugins/features I would love to hear them. I would like to use phpwcms in a similar way so it would be good to get more perspectives.
User avatar
Fulvio Romanin
Posts: 394
Joined: Thu 4. Dec 2003, 11:12
Location: Udine, Italy
Contact:

Post by Fulvio Romanin »

ionrock i forgot a VERY essential thing for plugins:

ALL PLUGINS MUST OUTPUT VALID XHTML

we can correct it, but our main aim must stay being accessible.....








...and yes, i know it's hard :)
Completeness is reached through subtraction, not through addition
ionrock
Posts: 279
Joined: Fri 20. Feb 2004, 17:04

Post by ionrock »

That is already the plan of course!
cguenther
Posts: 111
Joined: Sun 11. Jan 2004, 12:41
Location: Halle, Germany
Contact:

Post by cguenther »

Have a look in http://www.phpwcms.de/forum/viewtopic.php?t=1146.
There a patch can be found to include the version-variable and new replacment tag.
Locked