Hey everyone,

I know it's not really a hard challenge for a person with a little php and MySQL knowledge, but that's not me. So, I just ask here:

Does anyone have working plugins to get edito and wiwimod pages listed in that wonderful sitemap 1.2 module? They don't seem to be in the last release, but at least for edito, I think I've seen it in action somewhere. At www.herve-thouzard.com/modules/sitemap/, to be precise, but not quite sure it's working fine there either.

Thanks a lot,

Tobias

Never mind! I've switched my site to PHP 5.04 (my host gives me a choice), and that has reduced those scary PHP notices dramatically. In fact, I now only get a few notices from non-essential modules. And Tropical Mail does not like my idea at all, but that's no topic for this thread. So, I'll hang in with RC1 hoping the next release of 2.2.x will let me upgrade from here.

Ok, but actually, I don't want to downgrade to 2.0.x. I understand folks are still working on a stable 2.2 release, and I can wait out that development. I mean I've costumized a few things and installed some of the modules adapted to 2.2, and I foresee a lot of readaptation work even if they come up with an excellent downgrade script.
The question is just whether it's possible to get back onto a little more stable footing, from 2.2.3RC1 to 2.2.2 which, I understand, is the basis for current development (although I've also read something about future versions going to be developed on the basis of 2.0.x). My site seems to be working more or less OK, registering users and letting them login, post, and what know I, with 2.2.3RC1. I get a lot of messages in debug mode, though, which makes me worry, also reading what other people have to fight with even after weeks of seemingly stable operation.

So the question simply is: Is the database sufficiently backward compatible (between 2.2.3RC1 and 2.2.2) to venture into an attempt to just "upgrade" the system module backward? Or is that idea doomed to failure right from the start?

Only if there's a quick answer to that, otherwise I'll just try sitting it out and see what people come up with. Just came to XOOPS in the worst of all moments, I guess, between the release of "stable" 2.2.3 and it's downgrading to RC. But I'm hanging in here. Keep it up, guys, great work!

Bump! I'd be interested in some testimonials or informed opinions regarding libervis's question as well. Would it be more or less safe to install the 2.2.2 system module over a functional installation of 2.2.3 RC1 as a way to move back onto firmer territory? Not that my 2.2.3 wouldn't more or less work, but there're a couple of issues which I assume might have to do with bugs or something, and as 2.2.3 RC1 seems to be -- how do you say? -- deprecated, I assume taking the step back to 2.2.2 as a base also for future upgrades looks like a reasonable consideration. To me as a person who wouldn't be able to tweak and fix on my own. My site's just beta, or acquiring it's first users, and the people for whom I'm building it might be easily discouraged if I have to start over with a blank user database. Besides, "clean install" sounds like less work than it would be, with all the photos that are already in the gallery and bits and pieces in the database.

Also had that problem, in various modules. It's probably somewhere in the theme, but I tried to adapt style.css and styleNN.css -- to no avail... I gave up fixing it system wide (I think an OL should always be with numbers; for bulleted we have UL), and as I have just one list which really has to be ordered on my site so far, fixed it locally, defining and assigning a style inside the document in the editor. Of course, you have to make sure the editor you're using doesn't interpret your style definition as something else or stumbles over linebreaks you may have in your html code when copying it from some other editor. I use the newly free Opera for these purposes, that pretty much seems to automatically switch off all WYSIWYG editors

Thanks, that was quick. So, I understand I have to figure out whether the server supports an appropriate locale. I'm pretty ignorant when it comes to PHP but have tried with info I've found on the sites the two of you have linked to to run a little test. It was negative, but I'm not sure I did it right. What's a fool proof way to find out? And Lance, where approximately would I find Smarty's date function, or whatever you tweaked to get it done?
Still plenty of time, it's not going to make a difference until December (first three letters of English and Spanish month names I mean), and I can always fall back on something number based. So never mind if mine's just a stupid newbie question

Cool, but is there a way to get the three letter abbreviation of month names internationalized? My site's in Spanish, and where it belongs, dates are conventionally represented as, for instance, 27-Ago-2005, where "Ago" stands for "Agosto", as opposed to "Aug" in English. I'm sure you guys understand what I mean.

Wow, it seems I'm just not capable of sifting through all those different locations for preferences. Big thanks!

Ok, thanks, I guess I've been having a hard night. Of course, I've not been talking about Protector, but about DB backup & restore 3.0. I still don't find that module's interface block, but it's pretty obvious how to get there from URL: site root/modules/backup/admin/index.php

Sorry again, not my day, although it's my b-day

Five characters is too long, would be pretty helpful to be able to allow users to search for strings with four charcters. In fact, on my site there're loads of different names of groups which form the community for which the site is built, and some of them are only differentiated by a string that's four characters long.

Is there any setting I can change to allow for shorter search strings?