XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


« 1 ... 21 22 23 (24) 25 26 27 ... 41 »


231
barryc
Re: Making a field unique

  • 2007/12/19 17:10

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Yes, that's a good thought, and one that I have been considering. One issue is that if a member drops out, then rejoins at some later time, we re-assign the original member number. As long as we can overwrite the auto-assigned number that might not be a problem. This particular problem will become less and less important as, these days, when a member drops out we simply remove them from the Members groups in Xoops. If they rejoin, we just activate that members group. That way their old number is retained.

I'll play with auto-incrementing on my test site. Thanks.,

Barry
Barry Cooper
Sweet Home, Oregon
Topic | Forum


232
barryc
Re: Making a field unique

  • 2007/12/19 15:19

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Apparently I had not made it clear originally. The member number field in my 2.2.4 installation has already been created. Each time somebody joins the organization we register them on out site. The XOOPS database serves as our membership database. If a new member has already registered on the site we edit their record to include such things as their member number, join date, expiration date, etc. A couple of different people are involved in administering this aspect.

At present the database field for member number does not have to be unique so that it is possible to enter duplicate numbers for two different people. To avoid that we have to keep track of the numbers or look up what the last number used was. It would be nice if XOOPS would not allow the people doing this work to accidentally enter a duplicate.

I thought of make the field unique directly in the database and tried it, via phpmyAdmin, but it did not work for some reason. I'll have to try it again. Any advice on how to do that?

I also don't know what the behavior will be if I do succeed in doing that. Will I get a standard XOOPS message if a duplicate is entered?

Barry
Barry Cooper
Sweet Home, Oregon
Topic | Forum


233
barryc
Re: Making a field unique

  • 2007/12/19 1:28

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


No, because we have both members and non-members of our organization who are registered on the site. That means I have to have a separate field for Member Number. Unless I misunderstand you, I could not use <{$xoops_uid}> for both the user's normal ID and for the member number.

Am I correct?

Barry
Barry Cooper
Sweet Home, Oregon
Topic | Forum


234
barryc
Making a field unique

  • 2007/12/18 23:35

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


My XOOPS installation is 2.2.4. I chose to use that release because I wanted to be able to create some special fields in the user database. One of those is a member number. I would like to make that field unique, such that duplicate numbers would not be accepted and would return an error message. This would be similar to the email address field, which won't allow entry of a duplicate value. In the Fields admin pages one can make a particular field required, but not unique. Can anyone suggest a way I can hack this?

Barry
Barry Cooper
Sweet Home, Oregon
Topic | Forum


235
barryc
Re: Record IP of registrant

  • 2007/9/6 1:29

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


I'd be happy to try an alpha 2 version when it's available.

Barry Cooper
Barry Cooper
Sweet Home, Oregon
Topic | Forum


236
barryc
Record IP of registrant

  • 2007/9/5 21:27

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Is there any way that I can automatically record the IP address of an individual registering on my site(s)? I am being bothered by someone who is obviously not legitimate. He/she repeatedly registers using similar fictitious IDs and email addresses and always enters the same URL in the registration form.

I would like to determine what IP these registrations are coming from so that I can block them using the Protector module.

Thanks for any suggestions.
Barry Cooper
Sweet Home, Oregon
Topic | Forum


237
barryc
Re: Progress with Xoops 2.2.5, 2.3 and 2.4?

  • 2007/3/8 0:46

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Well, I must first admit that I haven't been testing the 2.2.5 RC2 release. I did download it, but the devs having said in November that the final was to be released in a few days, I didn't go ahead and install it on my test server, currently running 2.2.4. I will be out of town now for over 3 weeks, but when I get back I'll do some testing if it's still needed.

I guess the main point is communication. If testers are needed, why not post a message calling for some volunteers? Or did I miss such a call? I'm no programmer, but I can certainly try a release and report on problems that I might experience. I have no problem in being patient and getting it right, but the lack of communication makes users wonder how viable XOOPS is. I don't want misunderstandings on that front any more than the rest of the dedicated users and developers.

Barry
Barry Cooper
Sweet Home, Oregon
Topic | Forum


238
barryc
Progress with Xoops 2.2.5, 2.3 and 2.4?

  • 2007/3/7 23:36

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


I am wondering what progress is being made on the promised upgrades to XOOPS 2.2.5 and 2.3, and finally 2.4. My understanding is that 2.4 was to be the upgrade that allow the current 2.0.X path and the 2.2.X path to be finally merged again. I am one of the lost souls who upgraded to 2.2.4 way back before it was "withdrawn" as a recommended version. I did so because I needed the extra fields allowed in user profiles. I shudder at the thought of trying to downgrade to 2.0.16 and the profiles module that Mith produced for it.

Way back in November, when 2.0.16 was released, 2.2.5 was promised "in a few days". There has been no word since. Nor have any announcements about progress on 2.3 and 2.4 been made. I am becoming very concerned about the lack of progress and the lack of communication. Don't get me wrong. I am not an alarmist or a naysayer. I am a loyal XOOPS user. However, development seems almost frozen in time. The devteam.xoops.org site is now prohibited and there seems to be utter silence regarding work that might be being done. Is any work being done?

Inquiring minds want to know.

Barry Cooper
Barry Cooper
Sweet Home, Oregon
Topic | Forum


239
barryc
Pop-up usage agreement?

  • 2007/1/16 18:11

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Hi all. I hope someone can suggest a method to do what I'm about to ask.

I have developed a form, using Liaise 1.5 on a XOOPS 2.2.4 site, which is intended to allow members of our club to submit digital images to a photography contest. There are certain conditions that they must agree to (such as allowing publication of winning entries in our journal). I have written a statement of agreement that is part of the form. What would be really nice would be to have one of those pop-up agreement forms like the ones you see when installing software.

Has anyone done this? Could it be done within a Liaise form in Xoops?

Thanks for any suggestions.

Barry Cooper
Barry Cooper
Sweet Home, Oregon
Topic | Forum


240
barryc
Re: XOOPS Newsletter Mailer

  • 2006/10/16 22:04

  • barryc

  • Just can't stay away

  • Posts: 480

  • Since: 2004/3/20


Mith,

good to hear from you.

My scenario is an opt-in situation. All members of our association get the newsletter. Many have asked for receiving it electronically. We could just tell everyone to go to the web site and sign up (opt in), of course, but we want a mechanism whereby we would not send the paper version to those who opt for the e-version. That will save us postage and will reduce the work load of our volunteers. That's why I was looking for a way to send to specific groups. My idea was that our members would be in one group or the other. The "other" would be the group from which we download names and addresses for mailing paper versions. My intention was that future new members would, at the time of joining, opt for one or the other method of distribution.

I will look forward to some method of attaching a file to the "cover email". I hope it comes soon.

Barry
Barry Cooper
Sweet Home, Oregon
Topic | Forum



TopTop
« 1 ... 21 22 23 (24) 25 26 27 ... 41 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

124 user(s) are online (47 user(s) are browsing Support Forums)

Members: 0

Guests: 124

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits