Not to put a damper in preventing people from stealing your code, but the javascript that was presented is so very easy to get around, in fact, so easy I wouldn't waste the bandwidth it takes to add it to the HTML.

CoolPops

Mithrandir,

Yes! That is a much better idea. Makes more sense and works within the design principals of the comment system.

Thanks for suggesting that to me, I will make changes to my code to bring that about.

Thanks again,

CoolPops

I wrote a module that users post messages to a weblog. When a comment is left on that post, I want to send the owner a notification.

I thought of just subscribing them to posts automatically as they post them, but their Notifications list will become very large quickly, and largely unmaintainable. Therefore, I thought I would just send a notification based on a setting in the weblog setup, "Receive new comment notifications?".

I knew of the notifications handler I thought I would just trigger it with the specified user_id in the user_list array, however, when looking into it deeper it states in the dev wiki: "$user_list - if left blank, any user who subscribed to the event will receive notification. If you specify an array of users (an array of user id's), only those users will be notified (only if they are subscribed)."

So. I thought of one solution, but it's goofy and not very good programming, but on a comment post, I could subscribe them, send a notification, then unsubscribe them. This seems silly.

Is there a better way to handle this situation?

Thanks,

CoolPops

I don't have the API in PDF format or anything, however, a while ago I authored the Kickstart Guide for Xoops. It was intended as a multi-part series as to how to develop modules for Xoops. I only completed the first part, in which, will get you up and running with a module the right way. The module is very simple, it greets the person logged in, but has correct structure, uses XOOPS classes, accesses the current user to greet them by name, is multi-lingual, etc...

You can access the guide in PDF format:

http://jeremy.cowgar.com/files/xoops-kickstart-guide.pdf

The wiki it was located on is no longer in service, so this is the only usable format I have of it.

Hope it helps you out!

I am converting a non-xoops site to XOOPS and am importing 759 users, and 12,769 comments. Is there a way I can cause XOOPS to Sync all comments/posts so the people's Post and Rank will be correct?

I really don't want to edit each user and Sync each user manually. I have done quite a bit of programming with this conversion and some needed modules, so I'm not against even writing some sorta SELECT uid FROM xoops_users... $xoopsUpdateComments->forUid(uid) script either.

Thanks,

CoolPops

Unzip/tar them into the themes folder of your XOOPS install. Then, in the Admin Panel, Preferences, General, select the themes you wish your users to be able to choose from. You can also select the default theme there as well.

I think a problem exists with only two options for handling email address changes: Allow or Disallow. In today's Internet world, email addresses will change, therefore users *need* the ability to change their email address, however, on large sites this seems to be too much of a risk to just allow a user to change their email address. Now you have a basic Anonymous user who you can't contact, with a name and rights to do things on your website.

In coding an app for work I allowed clients to create accounts, validate their account (via email) and change their email address. The catch was, when they change their email address they are warned that it will cause their account to go into a suspended status. The system would place them into a suspended status and send a validation email to their new email address. Until that was confirmed (by a unique code sent to them), they could not access the site. Once confirmed, all was good. If it was not confirmed and they tried to login, they recieved a message stating their account was suspended due to an email change and they recieved an input box with the email address they entered and a "resend" validation message button. Therefore, if they thought they were going to become anonymous by chaning their email address, they now have the option of setting it to something real.

I know this does not solve all the problems (people can create an account, sign up, remove their email account) but it does thwart quite a bit and seems to make more sense than just Allow or Disallow email address changes.

I was curious if there would be intrest in this type of functionality? I would be willing to make the coding changes (no database changes would be neccessary) *if* I knew that it would make it's way back into the core.

Anyway, I also wanted to bring up the suggestion to see what people thought, maybe it would be better coded internally, but I did want to 1. Make the problem known, 2. Make a suggestion as to it's solution, 3. Be willing to make the coding changes.

Thanks!

CoolPops

How does one utilize the parsing and displaying of XCode, Smilies, etc? And the word sensoring option as well?

CoolPops

It's showing up and working on the form however it's the return value that's confusing me.

In the form I type in:

=========
Hello,

My name is CoolPops
=========

then save it to my database via a

sprintf("INSERT INTO ...%s",
$this->db->quoteString($_POST['dhtmlValue']));

In my database it is stored correctly. However, when putting that value into the DhtmlTextArea via:

$form->addElement(new XoopsFormDhtmlTextArea('DHtml Value', 'dhtmlValue', $entry->getVar('dhtmlValue'), 15, 80));

the textarea has:

===========
Hello,<br /><br />My name is CoolPops
===========

Then when saving again, the database then has:

===========
Hello,<br /><br />My name is CoolPops
===========

What am I doing wrong? I know something must be missing here.

Also, how does the word sensoring, XOOPS codes, smile faces, etc... come into play

Thanks,

CoolPops

Just to clear up any confusion, I used myhost.org as an example, it's not my site, nor am I affiliated with it in any way. I guess for examples I am going to start using localhost ... that's what I should have used to begin with, sorry.

I am using XOOPS to replace http://lifewithchrist.org not a site I do not have anything to do with, myhost.org.

CoolPops