check if the protector module hasn't blocked their IP addresses.

Herko

Quote:
I agree that it would be nice. But it's not mandatory at all.

Quote:

That is a direct violation of the GPL in itself. You cannot restrict what other people do with the code you've written, as long as they don't put any restrictions on their derivate works either. That's how the GPL works.

Anyone can sell XOOPS code. But they cannot retrict anyone who bought the code from releasing that very same code for free. this makes selling the code itself a shaky business model to begin with.
Better is to sell the services of development, design, customisation, support, training, hosting etc. Much safer bet, that is.

Herko

And there are other demo sites out there and in the making, one is even an official XOOPS demo site. Maybe you should ask Davidl2 and snow77 if you can help them out instead of making one yourself?

Herko

Please contact Edward LeVine at edward@buy-text-links.biz.

That's where we get all the links from.

And I'm sorry I haven't replied to your mail, it got lost in the huge pile I get every day (about 1500 SPAM messages per day... thats the price one pays for internet fame).

Herko

Like I said in my previous posts, it's not about generating good ideas. We have those aplenty. Probably enough good ideas to keep 100 full time developers busy for a whole year.

Thing is, we haven't got 100 full time developers with a year of dedicated XOOPS time to spend. So improving on the ideas probably isn't going to make them get realised any sooner.

If you can't code (properly) but have a bunch of good ideas, maybe you (in general) should focus on getting the resources to realise them. And that isn't done by trying to convince everyone your idea is the killer app for XOOPS. Because that's just more of the same, only bigger.

No, I propose you find ways to get the resources. Find funds, sponsorships, competitions, get IT students to make a proof of concept as part of their education, find partners to help you in getting those, find a developer who wants to do it for what you can offer, and include sustainable development in that (what happens with bugs, patches, support etc.).

Oh, and think less of what you can add to the core, and more on how you can get what you want in a module. That way the chances of success are bigger.

Just my 2 cents. Not aimed in particular at you, Wizanda

Herko

theres something wrong with the files in your system admin, because it is looking for files that don't exist on your system (and shouldn't exist). Download XOOPS 2.0.16 FULL and upgrade your site but uploading all files in that package (WITHOUT the install/ folder and files, and without mainfile.php). You'll be overwriting all existing 2.0.15 files.

Make a FULL backup (files and database) before upgrading, just in case.

Herko

The illegal part is that they removed the copyright and license headers in the files and distribute them under their own license. It is not illegal to take the XOOPS code, alter it, and distribute it, that's alright if you do it under the terms of the GPL.

That's basically our legal beef with them. If they add the headers back into the files, add their own credits for all their own work, and distribute the work under the GPL license (they can charge people for the software just fine), then everything is ok.

Herko

We suspected as much. PHPMySpace GOld is based on eXOOPS code, a long time ago. We are taking legal action to stop them from violating the GPL, but there isn't much more we can do.

Herko

Quote:
No, I didn't misunderstand you at all.

You want this:
WYSIWYG editor that writes pure BB-code. So the content is stored in the DB as BB-coded content.

What BB-code does however is change the content back to publishable HTML when the content needs to be displayed.

So: you propose wysiwyg -> bb code -> html
I propose: wysiwyg -> html

BB code was meant to *replace* (or preceed is more accurate) the complex and expensive WYSIWYG editors at the time (there are no good open source wysiwyg editors back then). You could make it easy to manage what is used and what isn't, and still allow people to add some special markup to their content.
Now, however, there are plenty of mature and manageable open source wysiwyg editors. Now you can do what you with them what you did with bbcode, but now you can do it even better.

SO, why add it on top of bbcode? You can santize the output even better then you can with bbcode (less coding necessary for that), you can manage rights, you can extend it easier.. Youhave the security of bb code, but you have so many advantages over bb code.

bb code isn't an end unto itself, it is a means to acieve something alse. If you focus on what you want to achieve, it's a logical step to *replace* bb code with a good editor like tinyeditor.

@frankblack: I know that I can confige tinyeditor to use a limited editor as default one. I love it

Herko

Tiny wins for me too. I just love its versatility. Easy to set up too.

Quote:
This I don't get. You would have the content put into HTML, converted into BBcode, which is converted into HTML by the textsanitser all over again? Now that's adding more useless work to the rendering engine for sure...

No, IMHO Tiny should have a limited default editor (like Wordpress has, uses TinyMCE too), thus prevening misuse. The content is stored as semantic xhtml in the db, and the system doesnt need to revert it back to html from bbcode, slowing it down.

Herko