Support Forums - All Posts - XOOPS Web Application System

11

Deleting Users

2009/3/3 21:34
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

Hi All,

Is there a way to batch delete users in 2.2.4? I have a membership site that needs serious cleaning up and deleting only one user account at a time will take hours.

Thanks in advance.

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

12

Liaise 1.5 vs Liaise 1.27 with captcha

2009/1/23 17:16
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

I'm using Liaise 1.5 on a XOOPS 2.2.4 site. I would like to install a captcha for security. I've searched, but can't seem to find posts about using captcha with 1.5 that also works for XOOPS 2.2.4. I do see a captcha available in version 1.27 but I don't think I can downgrade to 1.27 as I have existing forms.

Is there a captcha for Liaise 1.5? If not, is there a forms module like Liaise that uses a captcha for 2.2.4?

Thanks,

Cuidiu

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

13

Re: Site Not Mailing New Password

2008/11/28 3:42
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

Does this happen to any member or just one?

I've had this happen many times with some members of a XOOPS site. Their ISP rejected the emails sent from the site because the IP is on a spamlist. The site shares a mail server with a spammer and is often listed on the spam lists (they'll be moving from this host soon). So when the ISP receives email, sometimes it is rejected until the matter is cleared up and the site is de-listed. ISPs that usually reject are comcast and verizon.

Sometimes, the password email gets placed in a junk folder, as often happens with Yahoo email and the member says he didn't get the email when in fact, it's sitting in the junk/spam folder.

Hope

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

14

Re: Upgrade from 2.2.4 to 2.3.x

2008/11/25 18:34
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

I can't update my XOOPS sites either. I have two professional sites that make full use of the Display Name.

Quote:

ghia wrote:
As long as it is not implemented, the two branches of 2.0.x and 2.2.x are not truly united in 2.3.x and I can't update my XOOPS sites.

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

15

Re: Upgrade from 2.2.4 to 2.3.x

2008/11/21 2:46
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

I'm curious as to why an existing field in 2.2.4 would be considered a "feature request" in 2.3x? This was a mandatory field in 2.2.4. Does this mean its importance is quite low in the list of priorities?

Quote:

Mamba wrote:
Can somebody add it to Feature Request, with a link to this thread, so we don't track it back?

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

16

Re: Upgade from 2.2.4 to 2.3.x

2008/11/20 16:40
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

The Profile module is included but the field for the display name is not. I understand that a majority of XOOPS users out there thought it was unnecessary, but it is required for this organization.

Quote:

JAVesey wrote:
Not having been a 2.2.x user, my understanding is that the bundled "Profile" module is intended to replace the extended profiles part of 2.2.x

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

17

Upgade from 2.2.4 to 2.3.x

2008/11/20 2:12
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

I've done a few searches and come up empty so please forgive me if this has been addressed. I upgraded from 2.2.4 to 2.3.1 and don't understand why the option to use the display name field has been excluded. Would someone please show me how I can get this field to show now that I've upgraded? Our non profit association site requires the display name.

Thanks,

C

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

18

Re: Protector and SPAM URI

2008/8/13 0:03
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

Thanks for clarifying that for me, ghia_!

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

19

Re: Anyone using Protector 3.16beta with xoops 2.0.18.1?

2008/8/12 19:15
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

I need to upgrade from Protector 3.04 to the most current version. Is upgrading from version 3.04 complicated or is it a simple process of uploading the new files and updating the module?

TIA,
C

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

20

Protector and SPAM URI

2008/8/12 18:23
Cuidiu
Quite a regular
Posts: 358
Since: 2006/4/23

I hope someone can help me understand how this works. I am using Protector and show many of these in the Protector Center log:
URI SPAM /modules/contact/index.php SPAM POINT: 58
Many logged have even higher points. I assume this means Protector has prevented the spam from being sent through the contact page, correct?

Also, what triggers the log entry? I just sent a test through the contact module with an URL in the comment field and it went through. Are spammers doing something else such as adding something to the module's URL in the browser?

Thanks in advance.
C

[size=x-small]Working sites:
XOOPS 2.0.16 PHP 5.2.2, MySQL 5.0.24a-standard-log, Apache/2.0.54 (Unix)
XOOPS 2.2.4, PHP 4.3.10, MySQL 3.23.58, Apache/1.3.33 (Unix)[/size]

Stats
Goal:	$100.00
Due Date:	Apr 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Deleting Users

Liaise 1.5 vs Liaise 1.27 with captcha

Re: Site Not Mailing New Password

Re: Upgrade from 2.2.4 to 2.3.x

Re: Upgrade from 2.2.4 to 2.3.x

Re: Upgade from 2.2.4 to 2.3.x

Upgade from 2.2.4 to 2.3.x

Re: Protector and SPAM URI

Re: Anyone using Protector 3.16beta with xoops 2.0.18.1?

Protector and SPAM URI

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}