Quote:

I believe that the WYSIWYG editor used by TinyContent is SPAW, which relies on IE-dependant commands. I don't know that anyone has developed an open-source WYSIWYG editor that works cross-browser.

*dink dink*

Quick question: can you run XF-Section alongside WF-Sections, or do they access the same tables?

Glad someone posted something about this module...I can't seem to find it anywhere.

Anyone got a good link to the module? (I don't speak German, so I couldn't find it on the site indicated above. )

Quote:

We've been doing so as one option of what we do. We started out doing print, actually, and moved into web design (with an emphasis on the small business/non-profit market: clients who need a really simple, static site and don't have $500 to shell out for a consultation), and then with XOOPS started expanding a bit to support more complicated clients. Primarily, we've found that XOOPS works well when dealing with clients who need frequent updates to their sites, don't have a lot of money to pay someone to do it for them, and who have little or no technical expertise. A lot of our clients are political candidates or local political parties, for instance, but we've also designed sites for small retailers, restaurants, and--ironically enough--a vocational school.

We always make it very clear to the client that what we are selling is installation, customization, set-up, and technical support, and that we are <I>not</I> selling them the XOOPS package itself. There's a useful legal upside to this: in making it clear that we are selling the service and not the product, we make no implied warranty about XOOPS itself. So, if someone finds a security hole in XOOPS, hacks into the site, and does something to damage the client (creating some sort of defamation, for instance), we have no liability for breach of warranty.

Essentially, the relationship between XOOPS and the client is that same as the relationship between NetObjects Fusion/Dreamweaver/Flash and the user: it's just a tool that's been used to create the site.

Does that help any?

Okay, this has been driving me nuts for the year+ that I have been using Xoops, and I'm finally annoyed enough to ask it: what's with the bulleted lists?

Every single theme I've seen has the bulleted lists screwed up. Either the bullets appear way to the left of all of the other text (i.e., beyond the left margin) or the text doesn't wrap to match post-bullet indent like it should.

Obviously, this has something to do with the CSS settings, but nothing seems to make sense. Has anyone got a solution on this? (Or at least an explanation?)

Quote:

Perfect!

Thanks!

I'm working on a new theme and I'm having trouble figuring out how to do something. (I'm new to CSS, so I stumble a lot!)

I'm rearranging things a bit so that the module content appears above the center blocks. The center blocks all have the same kind of border around them as the theme for the main XOOPS site, but I want the module content to only have a border on the left.

I tried using a <DIV> tag and creating a new style in the style.css file (.CenterMainContent) and assigning it to the DIV class, but that didn't work. I tried doing the same thing by creating a custom TD style, and that didn't work. Then I just tried <DIV style="border: 2px 0px 0px 0px"> and that didn't work.

I've been Googling for tutorials that would tell me how to do this and came up with nothing. Anyone want to offer some wisdom?

Thanks!

I just discovered yesterday that placing an image map in the THEME.HTML file seems to break the whole system. Has anyone been able to do this successfully, and if so, how?

Thanks in advance!

Okay...[i]part[/I] of the mystery is solved.

Apparently, XOOPS doesn't want me to use an image map. As soon as I take out the image map, it works great.

Now the question is why not? And the other question is how do I work around this?

Quote:

Can't log in to get to it.