292241
jwhite
Bug in mailusers.php - re: sending mail only to users who request it
  • 2003/8/11 0:37

  • jwhite

  • Just popping in

  • Posts: 2

  • Since: 2003/8/11


Hello everyone,

While customizing and adapting XOOPS 2.0.3 to my needs, I found this bug which I haven't heard anyone else talk about yet (just about every other problem I've encountered has already been solved by someone else! ). What I'm trying to do is send e-mail messages to only those users who are interested in receiving e-mails from the site webmasters. This is accomplished on the user end by leaving "Receive occasional email notices from administrators and moderators?" checked in the user profile. When I go to send a message on my (admin) end, I'm checking "Send message only to users that accept notification messages (optional)" on the Mail Users page. Now this works, but not quite. The first user that is found is "lost". In other words, if it finds only one user who requests e-mails, no e-mails are sent. If it finds 10 users, it only sends e-mail to 9 users (users 2 through 10, or 1 through 9 if you start counting at 0).

I found the reason for this. In mailusers.php, located in /modules/system/admin/mailusers, there is the following code starting on line 164 (or thereabouts):

for ( $i $mail_start$i $mail_end$i++) {
    
$xoopsMailer->setToUsers($added[$i]);
}


The problem here is that $mail_start is never set. Perhaps it is set if PHP's "register_globals" setting is turned on, but if it's turned off, this variable doesn't exist. So the first time this for statement runs, $i equals nothing (NULL I suppose), and so the $added[$i] statement returns nothing. The next time the for statement runs, $i equals 1, so it works from then on.

So my solution was simple: add the following statement above that for statement:

$mail_start 0;


Now I have no idea if this breaks something, and it probably does. However, in my tests so far, it works fine. Maybe someone can suggest a superior fix now that this issue has been brought to light.

Anyway, I hope this helps, and I look forward to contributing more feedback, bug reports, and other stuff to the XOOPS community in the future.

Regards,

Jared White



292242
iconeb
Re: Download is broken
  • 2003/8/10 22:13

  • iconeb

  • Just popping in

  • Posts: 15

  • Since: 2002/9/26


Download is only for registered users because i would like to track anyone who's going to help in the development



292243
alinford
Re: Download is broken
  • 2003/8/10 19:17

  • alinford

  • Just popping in

  • Posts: 2

  • Since: 2002/10/31


I am also trying to integrate this into Xoops.

When I click the download link, I get this:
"Non puoi accedere a questa area
Se la pagina non dovesse caricarsi automaticamente, clicca pure qui"

Then it just returns to the same page.



292244
iconeb
Re: Download is broken
  • 2003/8/10 18:27

  • iconeb

  • Just popping in

  • Posts: 15

  • Since: 2002/9/26


In which sense? i tried to download the packet and it works. If you mean installing the module, i've written that it's still in an alpha stage and i'm looking for someone who wants to help me in migrating this software into xoops.
if you want to modify the core of the project itself i think you should contact its admin on sourceforge. if you want to talk about integrating into XOOPS you can write to me.
bye ;)
federico



292245
alinford
Download is broken
  • 2003/8/10 15:56

  • alinford

  • Just popping in

  • Posts: 2

  • Since: 2002/10/31


The download is not working.



292246
gronice
Re: WebSlave Project - a project managment tool
  • 2003/8/10 7:50

  • gronice

  • Just popping in

  • Posts: 30

  • Since: 2003/7/31


Hm, ok seams I've to rename the constants or find a way to use only one file for these constants. Thanks.

The options for what the block will show are at the block options

May be I should write a readme

Have fun

G'Ron



292247
Mithrandir
Re: WebSlave Project - a project managment tool

When I installed this module - no problems
When I made the first project - no problems
When I made the first task - no problems
--- And no problems with these actions

Then I added the blocks to the project pages - center-left and center-right and get the following:

NoticeConstant _ws_taskplaned already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 3

Notice
Constant _ws_overdue already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 4

Notice
Constant _ws_time already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 5

Notice
Constant _ws_notstarted already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 6

Notice
Constant _ws_completed already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 7

Notice
Constant _ws_complete already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 8

Notice
Constant _ws_progress already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 10

Notice
Constant _ws_deadline already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 11

Notice
Constant _ws_projectstart already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 19

Notice
Constant _ws_projectdeadline already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 20

Notice
Constant _ws_todo already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 21

Notice
Constant _ws_completedtasks already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 22

Notice
Constant _ws_resp_user already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 23

Notice
Constant _ws_hourstodo already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 24

Notice
Constant _ws_hoursdone already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 25

Notice
Constant _ws_status already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 26

Notice
Constant _ws_hours already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 27

Notice
Constant _ws_description already defined in /usr/local/psa/home/vhosts/ruffdesigns.co.uk/web_users/Mithrandir/modules/wsproject/language/english/blocks.php on line 28
and the Project Overview block doesn't show at all. Am I right in assuming that the Project Status block shows a random of the currently active projects? Or how does it work?



292248
gronice
Re: WebSlave Project - a project managment tool
  • 2003/8/9 18:08

  • gronice

  • Just popping in

  • Posts: 30

  • Since: 2003/7/31


Next update:

v.0.6.0
- include a status-block and a project overview block
- fixed some errormessages

Download v.0.6.0



292249
tayling
Re: cannot write to main menu
  • 2003/8/9 4:42

  • tayling

  • Just popping in

  • Posts: 86

  • Since: 2002/1/3 7


Thanks for that - is there a list of all permissions that need to be set? Thanks mate
Regards
Tony



292250
Herko
Re: cannot write to main menu
  • 2003/8/8 20:06

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


yes, the cache folder needs to be chmodded to 777 and the files in that folder need to be chmodded to 666.

Herko







Login

Who's Online

191 user(s) are online (116 user(s) are browsing Support Forums)


Members: 0


Guests: 191


more...

Donat-O-Meter

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

Latest GitHub Commits