71
Peekay
Re: how to remove many users and also remove many threads?
  • 2012/9/24 17:51

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Many thx for that update Irmtfan. Really useful info.

I agree you should avoid freeing up spammers email addresses, but although running a SQL query for 'level' and 'last login' isn't a problem, in the OP's case it may return several thousand rows of non-sequential user IDs.

I'm struggling to work out how you would get those ID numbers into the users group link table to associate them with a 'banned' group?. I also can't help thinking it would be better to delete those records to improve efficiency of the database?

A 'User Purge' (with a banned/delete option) would be a good core feature IMHO.



72
Peekay
Re: how to remove many users and also remove many threads?
  • 2012/9/23 11:28

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Quote:

irmtfan wrote:

I think the above is wrong because the actkey is filled when a user is registered but is still inactive.


Sorry. I didn't realise that. How are activated users identified in the DB?

I remember seeing your script a long time ago. Be interesting to know if it still works.



73
Peekay
Re: how to remove many users and also remove many threads?
  • 2012/9/22 18:36

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


The Xoops 'users' table has a row 'actkey' which would normally be populated when a new user clicks the confirmation email, so for starters you could delete the records for unconfirmed accounts. The SQL would be something like:

SELECT FROM `usersWHERE actkey '' OR actkey IS NULL


In PHPMyAdmin you can then just tick all the selected records and delete them. You might wind up with UID 1 being followed by UID 99 etc. but this should not be a problem.

You could also run a similar query on confirmed accounts to see if the 'posts' row was empty. You could delete those users too, but as Xoobaru points out, a lack of posts doesn't mean a user is a problem.

Accounts that are actively spamming your forum should be added to a banned group as Irmtfan mentions, but it is routine maintenance task really. Moving thousands of users into a banned group via SQL is well beyond me!

If you decide to tackle this, you will need access to PHPMyAdmin or some similar database tools. Your web host should provide this.

Obviously, you will do a full DB backup first.




74
Peekay
Re: Compatibility of XOOPS 2.0.9 and 2.0.13 with Windows 7/IE9
  • 2012/9/20 12:43

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


The only Xoops related issue I have had with IE9 is that it clears form data if a module includes a 'back' button. There's some more info in this thread.

I'm not sure from your post whether these are public sites, or on an intranet?. If they are public, I would highly recommend upgrading your Xoops 2.0.9 site as it had some vulnerabilities. AFAIK there are no issues with Xoops 2.0.13, but I would look out for modules that included the SPAW editor. Some versions of that editor were insecure and it was popular at that time.

If you are staying with a PHP-4 web server, most old modules should survive an upgrade to Xoops 2.0.18.2 which is stable and reliable.

The latest version of Xoops needs PHP-5.





75
Peekay
Re: XOOPS 2.5 - Optional Password Security Patch - v1.0.1
  • 2012/9/8 20:19

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Quote:
...You get a friendly engineer suggesting he can reset your password, the new password is instantly given to you by phone...

Well, that certainly is a pretty dumb thing for them to do. Do they have a suggestion box?
A thread is for life. Not just for Christmas.



76
Peekay
Re: XOOPS 2.5 - Optional Password Security Patch - v1.0.1
  • 2012/9/8 13:07

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


If Wishcraft's file changes improve security that's great, but I think the moderator should change the title of this thread to ensure Xoops users understand that it is optional. At present, it looks like a core-team security alert, which it is not.
A thread is for life. Not just for Christmas.



77
Peekay
Re: SCEditor: potential replacement for DHTML?
  • 2012/8/20 8:58

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Looks quite neat, but does it have/can it have Xoops image-manager support?. Also, with the current DHTML editor you can paste Javascript or PHP code, which is useful for adding a widget to a block for example.

Whichever editor is used, it would be great if the site webmaster could enable/disable Javascript support and toolbar buttons as prefs instead of hacking away at a config file.

Frankblack's Tinyeditor module was great because it enabled webmasters to present a basic BB code editor or an advanced HTML editor based on groups.
A thread is for life. Not just for Christmas.



78
Peekay
Re: xForms 1.21 Beta ready for Testing
  • 2012/7/26 15:49

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Hmm.. seems to be a problem with checkboxes?. I'm using 1.21 from Sourceforge. If you create 'Box1' and 'Box2' I get:

[ ] Box2
[ ] Box2

I am using Xoops 2.5.3. but I don't think this is a Xoops version issue, unless form elements are created outside the module and the core has changed. Can anyone confirm multiple checkboxes work properly with 2.5.5?

I loaded up the original Brandycoke Liaise 1.26 and that works fine.







79
Peekay
Re: Tinyeditor - how to stop paragraph tags wrapping around block elements
  • 2012/7/26 7:43

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


Glad it was of use.



80
Peekay
Tinyeditor - how to stop paragraph tags wrapping around block elements
  • 2012/7/25 10:03

  • Peekay

  • XOOPS is my life!

  • Posts: 2335

  • Since: 2004/11/20


An annoying default in TinyMCE is that if you paste code into the HTML window, e.g. an iFrame, it is automatically wrapped in paragraph tags. This makes it difficult to format the object and can sometimes break the W3C page validation.

There may well be a later version of Tinyeditor and the default may have changed, but if you have 3.3.9.2 and also find this is a nuisance, the default behaviour can be disabled.

class/xoopseditor/tinymce/settings.php

Just underneath:

"force_hex_style_colors" => true,


add:

"forced_root_block" => false,


Note that this still allows the correct creation of paragraph tags on pressing enter.

HTH




TopTop
« 1 ... 5 6 7 (8) 9 10 11 ... 187 »



Login

Who's Online

263 user(s) are online (174 user(s) are browsing Support Forums)


Members: 0


Guests: 263


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