11
RealyRoten
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/6/13 12:30

  • RealyRoten

  • Just popping in

  • Posts: 63

  • Since: 2005/8/18


butttttttttttttttt i just loged in a normal user not admin and i can access notifications.php
change my email address please to pattang2008@hotmail.com so i can get update notifications...

12
msdana
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/6/13 12:37

  • msdana

  • Just can't stay away

  • Posts: 817

  • Since: 2005/12/11


It seems like a module notification that you set as admin is not working, but as a regular it's fine, because the notification isn't set.

As a normal user, try setting notifications from each module, TESTING the notification page afterwards each time. Perhaps this can help pinpoint the module that's giving you trouble.

I had some notification problems using Catads and mx-directory BETA2. Once I found the culprit, fixing it was easy.

HTH
[size=x-small]If God is watching us, the least we can do is be entertaining.[/size]
Graphic Worx : Xoops Themes

13
fishspon
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/6/13 14:50

  • fishspon

  • Not too shy to talk

  • Posts: 164

  • Since: 2003/11/23


ok people, i don't know if this will help you as well, but the problem was fixed for me by uninstalling the catads module.

Disabling the module did nothing, but uninstalling it has brought my notifications page back into life!

Anyone else using catads?
[size=x-small]><> fishsponge <><
[HiFi Forum] [UNIX/Linux Forum] [Richard Hobbs][/size]

14
RealyRoten
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/6/18 8:56

  • RealyRoten

  • Just popping in

  • Posts: 63

  • Since: 2005/8/18


Quote:

fishspon wrote:
ok people, i don't know if this will help you as well, but the problem was fixed for me by uninstalling the catads module.

Disabling the module did nothing, but uninstalling it has brought my notifications page back into life!

Anyone else using catads?

I don't and i still have the problem Admin group do not get notification showing in there user block but do get notified via PM or e-mail.
change my email address please to pattang2008@hotmail.com so i can get update notifications...

15
DIDI5
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/6/18 10:29

  • DIDI5

  • Just popping in

  • Posts: 36

  • Since: 2006/3/24


You can use your CATADS module.
'simply switch off the notification and that CATADS will work mighty fine.

If how ever you have en-abled the nofication and still getting the blank page. (which you will )

No need to uninstall it.
Just switch off the notification of CATADS only, and then you go to your database and in the xoopsnotification table ((y'll find it)) delete all Notification for catads only .With that things will be back to normal.

Disable the NOTIFICATION for CATDS.
Then go to the DATABASE and delete all notification for CATADS that should work

The problem seems to be in the notification file for CATADs only and not the core site or anything else!
At your own risk tho...

16
Prooozella
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/9/2 23:58

  • Prooozella

  • Just popping in

  • Posts: 36

  • Since: 2006/2/11


I faced this problem for more than month but did not care!!

If I visit notifications.php in my site a blank page come on, but when I login as a normal user I see the notifications.php without any problems??
You are wellcome at MSNM:
al.hobayyeb@hotmail.com

17
msdana
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/9/3 0:50

  • msdana

  • Just can't stay away

  • Posts: 817

  • Since: 2005/12/11


Quote:
If I visit notifications.php in my site a blank page come on, but when I login as a normal user I see the notifications.php without any problems??


Turn on PHP Debug and see what error message you get. That *may* tell you what module is producing the blank page.
[size=x-small]If God is watching us, the least we can do is be entertaining.[/size]
Graphic Worx : Xoops Themes

18
allnewtome
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2006/11/23 22:47

  • allnewtome

  • Not too shy to talk

  • Posts: 175

  • Since: 2005/11/30


This has been a very useful thread.

I am using SMARTSECTION 2.12 RC1 (and now XOOPS 2.0.16) and the notification.php page was blank, but not for all users.

The debug showed this:

SELECT FROM prefix__modules WHERE dirname 'smartsection'
SELECT FROM prefix__config WHERE (conf_modid '2'ORDER BY conf_order ASC
SELECT title
short_url FROM prefix__smartsection_item WHERE itemid 170
Error number
1146
Error message
Table 'database.prefix__smartsection_item' doesn't exist


N.B. smartsection_items is a table name.

The content of prefix_xoopsnotifications included this:

52 |         |        170 item          approved         |       |        |
|     
53 |         |        185 item          approved         |       |        |


(There was also another one for the admin, that he be notified when article approved.)

I logged in as admin and deselected the "notify when articles approved" option.

I used sql to get rid of the rows above (delete from x__xoopsnotifications where not_id=52; delete from x__xoopsnotifications where not_id=53;)

Now it works fine.

I don't really need to have the "notify on approval" option, so just won't use it any more. I am assuming (perhaps wrongly) that that was causing the problem.

Perhaps this will help someone.

19
benzel
Re: Blank page appearing with "notifications.php" - Error produced from debug
  • 2007/2/18 16:12

  • benzel

  • Just popping in

  • Posts: 4

  • Since: 2004/8/17


FYI

I was experiencing the same problem. I turned on debug (previously a debug virgin) and found this message:

"Parse error: syntax error, unexpected '/' in /home/.../html/modules/PDlinks/include/notification.inc.php on line 8"

I am really only a VB Access guy, but this was simple enough to resolve. Sure enough, line 8 was "*//" instead of "*/".

Thanks for thread.

Ben

Login

Who's Online

147 user(s) are online (73 user(s) are browsing Support Forums)


Members: 0


Guests: 147


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