You're in for quite a little journey.

There is now real way to 'make it work'. You'll have to resign yourself to pouring over the code, line by line, and finding out whats wrong. This probably won't be easy (I say this since, if it was easy for you, you'd probably already have fixed it!), but it is possible.

One thing I've found when fixing a couple of older modules is that $this isn't mutable in php file. You'll find areas of code where $this->whatever = new value. In those cases, instead of refering to $this, you just need to declare a variable, instantiate it to an instance of whatever class you're dealing with, and try changing that instead.

I've had decent luck in that the modules I've fooled with just had a few lines like this that needed to be taken care of.

Good luck!

I am confused and baffled at the moment, so let me apologize in advance if this post just kind of wanders all over the place...

I have the following installed:
- XoopsEditor (version 1.10, I think since it has TinyMCE included).
- XOOPS 2.2 Frameworks (version 1.01 apparently)

First of all, are these the latest versions?

Beyond that, I'm having trouble with the Koivi editor. I use it pretty much everywhere I can. There is one place where it works pretty well. In every other location on the site, the editor exhibits the following weird behavior:

--- Koivi Weird Behaivor ---
To see it, type "hello", then *Enter*, then "there". Finally, click the bulleted list button. If "there" becomes a bullet, then that's great!. If "hello" becomes a bullet with "there" moved over with it -- then that's the 'bad' behavior. Try as I might, I cannot get Koivi to separate paragraphs without switching to HTML mode and manually fixing up the p tags.

Because one module get's it right, I assume that one or the other has a working Koivi, while the other does not (XoopsEditor vs. XOOPS Frameworks).

Has anyone else had this problem? If so, why am I experiencing it?

In your opinion, which is the better solution, the XoopsEditor or the XOOPS Frameworks. I'd love to see a discussion of the merits of the two and why the future direction is supposed to be with regards to this.

As an aside, TinyMCE seems to be very solid and stable. It's only lacking quote/code support (maybe I can add those?).

Help please!

Sorry it's taken me so long to get back to you.

I think, in order to solve this problem once and for all, we need to take a sledgehammer approach :)

This may be overkill for you, but it should open up all the features of the module to your article submitters.

On line 66 of submit.php, change 0 to 1. It should now look like this:



Please note that this basically overrides any filtering that gets done. Your article submiters will be able to directly approve their stories...whatever the content. You might, however, implicitly trust them. In that case, this wouldn't be a problem.

The 'real' solution for you is one of the following:

a) live with the fact that the author of the module didn't intend extended text to be usable by general site users.

b) pour over the code in submit.php and move anything related to the extended text field outside of the 'if $approveprivelege' blocks. To find this stuff, you want to look for 'bodytext'.

I'm not really sure why the extended text was limited in this way ... but that's what available.

Hope this helps!

I've noticed the same problem from time to time lately. I have no idea what might be wrong though...just sharing the pain.

OK, obviously I clicked the wrong button and posted this as a new topic instead of a reply. Sorry about this.

Anyway, this was meant to be a reply to this thread instead.

Thanks for the comments...

I'll contact the people involved and see if I can get permission. I'll just about guarantee you, though, that they won't sign off -- so don't expect this theme to show up anytime soon!

If, however, they decide that it is OK to copy their look so blatantly, I'll post back here and let you all know.

This doesn't really answer your question directly, but you could always show block data along with your default module to achieve something close to the same effect. For example, you could enable the Recent News Topics block and place it top/center while making your forum the default module.

Your users would then see recent news articles at the top of the page and the forum just below that. If no blocks exist that provide the exact look you want, you can always create a custom news block that shows exactly what you want it to.

This is all pretty basic XOOPS stuff -- sorry if I'm insulting your intelligence.

I had worked on a theme over the holidays last year that I never got around to releasing. I actually do make use of it behind a firewall -- but haven't worked up the guts to release it to the community.

I do have a good reason though. This theme (called glossy) was created by me as an attempt to copy the look and feel of Stardock's beautiful web site. Once I nearly finished with the work, I realized that this idea of copying someone else's work idea might not be too cool. So I never really did anything about it.

There are some differences, of course. Stardock's web site isn't based off a common php-based CMS. Rather, it's all in house custom ASP code. Furthermore, their slick look is achieved with fixed sizes everywhere. I wanted to adapt the look to XOOPS and alter the code/graphics, so that things could grow and shrink to fit the screen.

Add to all this the fact that the trend lately is for everyone to favor CSS-only themes. Well, I can tell you that Glossy does make judicious use of tables. So if you're a CSS only proponent, you'll hate it just for that.

So what's the consensus here? Am I a tyrant and a thief for blatantly copying someone else's hard work? Or, rather, is it simply an homage to someone's outstanding effort and not offensive at all? Let me know what you all think. If it's not considered bad form, I'll try cleaning up the theme and releasing here on the site.

Here's a couple of screen shots (full size -- sorry if you hate that):

trspice,

It's odd that you would be having so many problems with this. On my local computer, I have the following set up:

- XOOPS 2.0.16
- News 1.53 (with the HTML Config Option applied)
- PHP 5.2.0

With this set up (I only have news and the latest cbb installed), I don't experience the problem that you apparently are having with the extended text:



Notice in the image above that rlankford (not an admin) is logged in and has posted an article with extended text present (hence, the availability of the 'read more' link). When I click 'read more', I get this:



You can see the extended text. You can also see that it has been altered. This was done with the rlankford account with no problems.

I don't know what's going on. Is it possible that you've been thrashing about in the news files and have caused a problem?? Maybe staring over with fresh News 1.53 code might help??

Best of luck...

Quote:



That's what happens when you write the second half of your sentence 5 minutes after you write the first half! No more interruptions for me!