XOOPS patches are for updates only!

So, if there is a security issue, and the core team fixes the problem, the version number goes up.

If you look closely, you will notice
Quote:
... everything labelled as a patch, has two sets of numbers, ajoined by "to"...meaning, you go from one number to the next version, by patching the first version number, which leaves you with the last version number.


An example. Let's say, you had installed XOOPS a couple of months ago. Then you would have an 2.0.7 installation.
Now you want the latest version, so you would need the "XOOPS 2.0.7 to 2.0.9.2 patch"

Now let's say installed your XOOPS system mid december, and have 2.0.7.3 installed, then you would use the "XOOPS 2.0.7.x to 2.0.9.2 patch"

And if you installed in January your XOOPS system, most likely it would have been 2.0.9, which you would now have to patch with "XOOPS 2.0.9 to 2.0.9.2 patch"


Hope this clarifies

@wardick: If anonomous is set to submit, it will appear, if not it will not appear, only the "News" link will appear!

Sounds like you haven't set access right for those modules...

(Sys Admin -> Groups)

I just stumbled accross this thread, so I haven't read all posts yet, but I need to point something out:

Mithrandir wrote:
Quote:

While this sounds reasonable, it can get you into legal trouble, if
- the code is not GPL, as requiered by client!!!

Then you will either:
a) need permission from the client, to use the code in othe projects of yours
b) arrange with client a GPL license for the code you want to reuse


This is my reasoning, why I will never take on work from client, that is not willing to support Open Source (and why I fight against current IP laws, and software patents)!


In case someone want to do some reading on Open Source reading, O'Reilly tries hard to be a profitable business, and sticking to the idea of freedom, and provides for free an online version of the book Understanding Open Source and Free Software Licensing


...back to reading this interesting thread...

...with that animated gif in your signature, sure thing

Though, as with themes like the one you are using, which use images for a lot of design stuff, this task becomes more work intensive.

For basic themes, this would do:

A Short Guide For Changing Theme Colours

1) using a colour picker tool (Firefox/Mozilla have web dev extensions for this task, or you can use as Win user the freeware app Color Cop, Linux comes with these kind of tools ), check the hex number of the colour you want to change

2) open the css file in an editor that comes with a decent findAndReplace tool (chami's HTML kit doews the job, but while there is a free verion, this is NOT FOSS)

3) now just enter in find the hex code you want to get rid of (e.g. that eye shaddering yellow{hex=#ffcc00} and in replace, enter the colour you would prefer (for example a pleasant light blue {#6a88ff})

4) repeat 3) for all colour you want to change (which involves a little hunting down {don't forget to check the link hover colours, and forms, the stuff only obvious when using the system, and not only looking at some content})


Now you have the images to deal with, if you don't have thousands of dollars for Photoshop (and/or don't like warez), GIMP will do the job.

Depending on how many images have been used, this might turn out, to be the heaviest regarding the involved workload.

Open each image you can find in your theme folder, change the image from palette to rgb values, and use the colourize tool (gif images don't use all available colours, but a defined pallette of colours, which most colour tools can't work with, as they like to have access to all colours).

Sorry if this is too brief, but I can't write a whole tutorial about image manipulation.

Hope this helps anyhow...post any questions that might arise, and I will try my best to answer.


Oh yes, and try to contact the guy who created that theme, and ask him if he wouldn't be interested in helping you creating different colour schemes for his theme. It would be great, if we had more colour options when it comes to themes. So please don't forget to provide us with a copy of your work and efforts {thanks in advance }

Enjoy!

MarcoFR/Ackbar:

I've noticed this group, and think it's a great project. Unfortunatly they are so fresh, that their site doesn't contain much info.

In some ways intersting, I found this link they provided to the PHP Manual Security pages, which displays the main problem with security and app development: [the developer! Meaning, one can provide the best information, and still people wont implement, what has been pointed out.

DonXoops:

And yes, no matter what we will be doing to the core, the vulnerability is with 3'rd party modules. Especially as people like myself, use XOOPS as means to teach themselves web application development skills.


Thankfully, two new XOOPS projects (at least this is the impression I have), will most likely assist us with this problem (eleviating most of the need for luck; we still need it though, to get the people together to take care of the accompaning workload ):
- Security Group
- Quality Control

To keep up a positivist attitude, I believe there are a couple of other things we could do.

1) on dev.xoops.org wiki, have a page dedicated to "basic security measures" when developing, such as checking all input, never to use "Globals On", etc..., with a link placed amongst all those other "Manuals"

2) have a special forum on dev.xoops.org dedicated to security questions ("hey guys, could you look at this code, and point out any possible security risks?" "Ahh, this might be an offender" "Why" "well....." -> discussion)


Too often do dev's believe, thought once about security, job done. Reality suggests, that checking security is an ongoing issue, which is difficult to implement as dev, as our interest lays first with getting a certain task done, then we worry about how it looks and works, the period at which thoughts regarding security usually/might kick in.

There is no 100% security, but there is 100% security awareness, which we should strive for. And judging by this thread, we are on the right path

Is she using a computer with cookies turned off?

Easy answer: NO

Lots of coding answer: Probably

As I believe what you want is something like this:

block(00) -> position:center-center
block(01) -> position:center-center
block(02) -> position:center-right
block(03) -> position:center-center
block(04) -> position:center-left
block(05) -> position:center-center

You would need to be able to controle blocks by their id, and I'm not sure how to do this....

Another issue is, that you want center-center blocks to once display with width=100%, and in another case with width<100%, which makes this idea a hell of a job...IOW, don't try this, but come up with another solution for your display/design desires.

What about VoIP numbers?

I believe they should also be collected, but in specialized fields.

Just my 5c's...

Favicons are also called Shortcut icons, which is the term actually employed by W3C (the term favicon was a MS creation, taken from favorites {US spelling}, instead of bookmarks).

In your theme.html file, you will find in the header section (HTML doc's are divided into a Head, which has additional info regarding the doc, and a Body, which contains the to be displayed content), the following code, which implements the Shortcut icon display:



So theoreticaly you could use a different shortcut icon for different users, using a little SMARTY.

Example Code:

...as to why one would want to employ this: gives a graphical cue, if you are loged in as admin!


Besides the link provided by tjnemez (chami's tool is very nice, and gives a quick fix), may I point to a nice app called AWicon (done this before), they do offer a free version, which I use frequently.