I'm setting up a new site and am using xoopsfactory's myxoops CSS based theme. It's working fine so far, except that I can't figure out how to get CBB to show up properly in Firefox. Works fine in IE. Basically, there is a big white space gap. I've played around with the CBB CSS and have changed the theme preferences from default to myxoops to none, etc. but haven't stumbled on the solution. I'm not so great with CSS.

Any suggestions would be greatly appreciated.

See the difference between Firefox and IE (problem in Firefox):

http://vinolove.com/modules/newbb/

Thanks.

deleting the row seems to have done the trick!

Thanks!

It's funny you should mention Microsoft. Your analogy is understood though you state it incorrectly. It would have been more apt if you said that using Microsoft FINAL is really like testing a BETA and so no complaints if it sucks. Everyone in the world now has enough experience with Microsoft to understand this.

I would be willing to say that XOOPS had a better image than Microsoft on this front PRIOR TO 2.2. Even still, I'm sure many had second thoughts about upgrading. I certainly did. Ironically, I upgraded specifically because there was a 3rd party module that had more features for 2.2 than on 2.0. Features my users were asking for. Features that work. I've had no problems with 3rd party modules on 2.2. I made sure my modules would work. My problems have been and continue to be in the core. I cannot downgrade without losing module functionality and pissing off my users. . at least, those who haven't left because of the bugs. Belive me, I would if I could.

You can rest assured that I won't be downloading 2.4 for at least 4-6 months after its release as FINAL.

You are right about one thing. It would be stupid to trust that a XOOPS FINAL is anything other than BETA.

Ok, Chris03 - you obviously haven't been paying attention in your couple of years on this site. . I will spare you the details and try to minimize my rage at your idiot post, but you clearly do not realize that the "not for production sites" is a RECENT advisement due to the unstable nature of 2.2.x and came only months after xoops.org was promoting 2.2.x upgrades.

That NOT FOR PRODUCTION SITES should actually read:

"Our sincere apologies to the thousands of Xoopsers who upgraded to XOOPS 2.2.x over the several months we were promoting it. We should never have released a product as FINAL that was not properly tested, and we realize the damage doing so has done to XOOPS user websites and the XOOPS community. We hope you will continue to bear with us as we try to fix the most egregious bugs in 2.2.x and produce an upgrade path to a stable 2.4. Be advised, however, that we're not really focusing on creating a stable 2.2.x because so many of our developers have left over the last few years in disgust. Given this resource constraint we are focusing on building an upgrade path to a stable 2.4 instead. So, if you can, you should downgrade to 2.0.x, but we understand that this is impractical for many users. Again, our apologies for this. We're doing the best we can. For new users, 2.2.x is NOT FOR PRODUCTION SITES, use 2.0.x instead."

Petkove - Yes, a lot of things changed from 2.0.x to 2.2.x and those changes are certainly the cause in some way of the errors in 2.2.x. If you have the stomach to downgrade to 2.0, that is certainly the best way to go. However, this may be impractical for hundreds and perhaps thousands of us who run highly trafficked sites and cannot risk potential additional complications or errors introduced by downgrading.

If it's a new site or a recent upgrade, I would downgrade.

thanks so much for your help! I changed the line, updated the module but still get the same error message. . . I also tried the line you suggest but with only one '&' thinking this might have beena typo, but still the same. . .

I appreciate the attempt though.

petkove. . i was in the process of responding to your "invalid session" post and then I just got frustrated to have to even think about this. then, i saw your post to my thread basically about the same thing.

you are correct. it is SAD that no one cares about this issue. But, the truth is that this is one of many things that no one cares about really. There have been bigger fish to fry over the last year and this bug, while severerly damaging to xoops, only impacts a very small percentage of sites (ergo. . you are on your own).

Part of the reason for this is that the expertise in the area of security and tokens and sessions is limited to a few (unknown) XOOPS developers. they have never publicly acknowledged this bug, even after being reported as a core bug. I reported the error in December 2005 and it was never assigned to anyone. . as is the case with most bug reports:

http://sourceforge.net/tracker/index.php?func=detail&aid=1394483&group_id=41586&atid=430840

good luck.

my advice is to try to see if it impacts different browsers or, in my case, is related to opening new browser windows or using multiple browsers at the same time (i.e., fox and explorer). then advise your users accordingly on what to avoid.

I couldn't find anything on this with search, so I'm posting here. I'm running xcgal 2.02 on a few sites and have just noticed a consistent error.

When uploading a picture to a public gallery and not logged in as a user (i.e., an anonymous upload), the upload takes but results in a white page with this error:

Fatal error: Call to a member function on a non-object in /home/hotdogbl/public_html/modules/xcgal/include/picmgmt.inc.php on line 146

Has anyone seen this and know what the fix is?

in the WP admin area, click on plugins. underneath the nav bar with "plugin" you will see another horizontal nav bar with "akismet configuration." this is where you enter your API key obtained from wordpress.com. Once you do this, you will find the holding bin for comments and posts identified as spam under "manage" then "akismet spam" or "comments awaiting moderation"

your other pages should not be blank.

bump. this would be a good feature. . .

bump! I'm looking for something like this also.