k... this thread has been long enough, so I'll bring my 2c shortly:

- I agree the real name may be a good thing, but that is should not be changed
- I also think that, security-wise what it brings is limited (now: it's not "nothing", but it's limited)
- The default minimum lengths set for new users login/pwd in the core should be changed (by default it's 3 and 5 chars, which is not enough)... admins can change them, so no big deal, it's just that by default XOOPS should be installed with something like 6 and 8.
- We cannot "expect" users to use a safe complex password, but we can force them Maybe adding an option for admins to enforce complex passwords (so dumb ones are refused) would be nice too (I'll try to find a way to implement that one)

skalpa.>

Personally I think the easiest way is to use the flashVars method (at least if you don't want to send a huge amount of data to your flash movie).
For instance, if you write something like this in your template:


you'll get a 'title' variable available in your flash movie, containing the content of the 'xoops_sitename' template var.

skalpa.>

The answer's here.


skalpa.>

Quote:

That's incorrect. When 2.3 is deemed stable it will be renamed 2.3 beta 1. If that had been the case I wouldn't have released an "alpha" version, but would have called it "2.3.0". Sorry if the roadmap didn't make this clear enough (I thought saying one of the goals of 2.3 was to give a better version for 2.0 users was enough).

@xephon: we cannot let anybody in a dead-end, so whatever happens there will be a way to update your 2.2.x site if you make one. Now, it just that it will be longer to come, so unless you really need the features of 2.2 and don't care about its problems, it's recommended to stick with the latest 2.0 for the moment.

skalpa.>

Quote:

ROFLMAO

1) I agree these things have been more changed into some kind of nonsense marketing arguments, but it doesn't mean they're not useful.
2) They allow to make pages that get displayed faster (that's the "perform" part), and allow us to changed/enhance these pages appearances more easily (that's the "look").
3) Usability has nothing to do here. It's not a technology or whatever, but a philosophy. It's about respecting people with disabilities, and ensuring they can access your content, as everybody. I guess some people may find it better to kill all those "inferior" humans to create a perfect world where we wouldn't have to care about them, but I don't think it's the good way.
4) CSS is more the "material" we use to build pages than only a technology.
2 of the 3 little pigs didn't care about the material they used to build their house. The story shows they were wrong.
5) Don't believe every single stupid article you read on the web. The fact one guy was able to install a blog application or to pay a hosting company for such a service, doesn't mean he's smart or what he says is right.
Actually today, it would be more meaningful to start a website about "stupidly lame articles that suck" instead of "web pages that suck".
(BTW: just looking at the way this guy page is layed out should have been able for you to realize that what's in his article couldn't be serious)

skalpa.>

I'm publicly opening the new development site, which will become the one of only source of information about the XOOPS developement from now on.
It is far from being complete, but I believe this is the way things should be: give something to everybody even unfinished, then build progressively.

The devlog will be updated daily as much as possible, and alpha releases will be published there too.

A few things to note:
- MSIE compat has not been fixed yet, so please use a real browser to go there. This will be fixed later on (but this is not the highest priority right now).
- Informative posts about the dev roadmap and the 2.0/2.2/2.3 development future will be published tomorrow, so please be a little more patient.
- This is a worktool, not a support or discussion place. There are forums for this and if the comments feature is misused, I'll disable it.

It's running on 2.3.0-alpha1, that will be published in the forthcoming days, and the theme used is a slight modification of the new default one

Again, I'm sorry for this not being as complete as I or you would want, but that will get better day after day.

XOOPS development site

skalpa.>

Quote:

Last modification: Rev 100 - 2005-12-13 05:35:42 +0100 (Tue, 13 Dec 2005)

Wash the **** out of your eyes...

skalpa.>

Sorry about that but I'm not coming here often, and somebody had told me this information had been made public several days ago (man... are you sure you know what what 'since yesterday' mean ? ).

We're now using the berlios.de SVN service to host the code repository, and it's there:
svn://svn.berlios.de/xoops4/
(I registered the project as 'xoops4' months ago on berlios, coz 'xoops' was already taken).

The 2.3 work branch is located in:
/XoopsCore/branches/2.3.x/2.3-main/

And those of who would like to follow everything can subscribe to the SVN mailing-list.

Also, the dev site with all the things people are expecting is coming in a few days, with the 2.3.0-alpha1 release. It's not here yet coz I wanted it to run on 2.3.0a1, so I logically had to make it before the site.

skalpa.>
PS: Berlios is only used for SVN, everything else stays on SF.
PS2: There's a readme file, read it before trying anything.
PS3: If you need support with that, then you'd better wait for a few more days for a real release to be made.

This is due to PHP5. The problem will be corrected in the next release.
In the meantime, you can edit /install/class/mainfilemanager.php
and change:
Quote:
to
Quote:

Also, jd's right about MySQL5. I'd suggest you use MySQL4.0.x . Full 4.1 / 5.0 compat is planned but it's not finished yet.

skalpa.>

Quote:

I'll look at it, but if it's as good as it looks it will soon...

Thanks a lot

skalpa.>