Hi

Some of my smartsection articles are not visible to anonymous users.

On the home page I have the "recent comments" block. It displays the title of comments on ALL articles. E.g. "Re: private article..." Even for anonymous users.

(However, anonymous users cannot read the actual comment.)

Is there any way to alter the "recent comments" box so as only to display the title of the comment if the relevant article is also visible to the user?

Thanks again.

You could do that with modrewrite. Google it. I hope that points you in the right direction but unfortunately I don't understand it!!

I have XOOPS 2.0.16 and have just upgraded from cbb 3.0.4 to 3.0.8. Php 5 and MySQL 5.

I also saw the "error 134 from storage engine" when upgrading. It still said "upgraded successfully" - and appears to work OK.

Any error message worries me. What should I do?

(I will upgrade to 2.0.17 once the problems with that release have been ironed out, but I am upgrading my modules now.)

Thanks!

Hi there, this rang a bell so I searched Google for it and came across a post of my own... hope it helps!!!

https://xoops.org/modules/newbb/viewtopic.php?topic_id=37773&forum=15&post_id=224379

I use 2.0.16 now and the problem doesn't arise any more.

I couldn't get Formulaire to work at some stage (can't remember why). Have a look at Liaise:http://www.brandycoke.com/home/modules/cryptica/showfile.php?file_id=31 I use it with XOOPS 2.0.16 with no apparent problem.

Hi there

I'm using XOOPS 2.0.16

Google provided a link to a page of mine like this:

smartsection/item.php?itemid=50&keywords=

The page text displayed as:

r /br /br /br /a href="http://www.thelink.co.uk/"/

When I enter either of these into the search bar it works fine:

smartsection/item.php?itemid=50
smartsection/item.php?itemid=50&keywords=xxx

I assume that, because XOOPS would never come up internally with keywords=(blank), this is a mini bug that hadn't been noticed.

Any advice?

I'm pretty sure the hack itself works with 2.0.16 but the files supplied are older versions than the 2.0.16 files. Does anyone have the 2.0.16 with the hack applied?

By the way, how do you get a message saying "You have X new PMs" (It's on the forum somewhere I know...)

OK here is what I know.

Here is how the notifications table is structured:



And here is an example if its content:



not_id is the notification identity number. When a notification is cancelled, XOOPS deletes the relevant row (and doesn't change any of the other not_id row numbers). New notifications are given the next highest not_id number (auto_increment) rather than filling in any gaps.

not_modid identifies the relevant module. On my site 2 is smartsection and 4 is cbb.

not_itemid is module-specific and identifies the relevant item. Most here are 0 as they refer to the module generally, but note not_id 54 where the not_itemid is 113 (the thread number to be notified about).

not_category and not_event explain themselves and are module-specific again.

not_uid identifies the relevant user by his user number.

not_mode - well, I honestly don't know what it means, but stick with 0 and you can't go wrong!



For 20 users you could easily use MySQL commands to add 20 rows for 20 new notifications. For more users I suppose you could write a PHP script to do it automatically. If you do that then submit it here! It could make a good module.

To delete users who haven't logged in for a while you'd just need to delete (or not) the relevant prefix_xoopsnotifications rows depending the value of the last_login column of the prefix_users table. I haven't time now to think it through fully.

I don't think that the table is referred to elsewhere so don't think there would be any problems with adding to it via MySQL (back it all up first though!) I've deleted rows with no problems but haven't had to add any yet.

Good luck!

As far as I can see it you have these options:

1. Tell your 20 members how to log in and change their own notification settings.

2. Log in using their usernames and do this if you know their passwords (this is what I did in the end as I also had 20 users to change!)

3. Change the notifications table in the database. As far as I see it's as simple as adding one row for each notification. I don't think it's cross-referenced anywhere else, so I don't think you can break anything by doing this. Recently I deleted a row from that table (it was causing a problem on the notifications.php page) and it didn't seem to have any knock-on effects.

I can try to explain option 3 if you feel it would be useful. If anyone knows that that option would break anything then please say so

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:



N.B. smartsection_items is a table name.

The content of prefix_xoopsnotifications included this:



(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.