Notification Settings

[Midnight Modding]

Eh, I've had my notification extensions done for ages, but just noticed in notification settings there is nothing there related to my app at all. Did I forget something or it won't show them until the app is actually built? Most eevrything else works in_dev before the app is actually officially built, so I don't know why this would be any different... Hmm...

ALso, personally, I wish the notifications settings page would be improved because having all settings one after another, rather than in tabs, is going to get messy. This app I am working on is so huge it has a ton of necessary notification types. So it will be a long list even on its own. I thought about combining them into basically only 2 or 3 notification keys, but then it would be messy code-wise, rather than looks-wise and it took me so long to do those, I'm sure not redoing them at this point.

[bfarber]

As long as your Notifications extension returns the appropriate data, you shouldn't need to build your application before your notification options will display.

[Midnight Modding]

oops, I forgot I have checks around them, so I probably didn't pass the checks.

[Midnight Modding]

I like most of the setup of 4.x, but the notifications setup is very frustrating. It building the inline notification on the fly as it's opened causes all kinds of frustrating situations. I have several situations where the notification is about a current situation, which later is no longer true or relevant anymore.

In 3.x I could just set the message, send it, done. I think of a notification as something about a point in time, not something to read differently depending on when it's opened.

I thought about merging or deleting, but those are not ideal, either, and plus I really like notifications staying there, even if not relevant anymore, just for research purposes, looking back on the past.

So I guess my only choice is to store extra data (with the notification, of course) and then check the item when the notification is opened to see if it still matches the previous situation. It's a real mess doing it that way in a couple of my particular uses.

Also, as I have said before, I really wish the notifications settings page would be broken into separate tabs for each app. I have a TON of necessary notifications for this app and it's going to look like a mess. In 3.x I grouped many into several notification keys, but I interpreted docs for 4.x as saying I should do them all separately, and now it's too late to change the setup. Plus I thought it would be nice for users to have control over exactly which ones they receive, but there are so many it's an unbelievable ordeal.

[Midnight Modding]

As far as the settings setup, maybe it's not so horrible being on one page, but would be better if the application names stood out a bit more. I still think a separate page and having separate tabs per app would be better, though. (especially for mine. maybe most apps need a lot less than I do, but mine has a lot)

[Midnight Modding]

Didn't someone (I think Brandon) say that notifications are auto deleted when an item is deleted? So it will only do that for content items? (I have a few where the main item I send is not a content item, just a plain active record).

For my most annoying situation, maybe I should just delete the notifications manually when they change enough to no loner be relevant...

[Midnight Modding]

Are notifications only "for" actual content items, actually? Maybe I need to look through this again... i am thinking docs said it didn't have to be. In a few cases I set the item as a non-content-item, but haven't got to the point of testing them yet.

edit: just thinking without yet looking, I'd assume it would work with it not being a content item, as it would just call load(), which could be any active record...

[Midnight Modding]

Sigh. I looked myself. I see it deletes them only for content items and just the way the code is (I haven't backtracked through the whole process), I get the feeling that $item really needs to be a content item?

So if I made $item be an AR class related to the content item, is it going to throw an exception and not store my AR class? So i'd need to change those to have $item always be the main content item and use the extra data to store the other table's row?

I did it this other way because it's technically "about" an offshoot aspect of the content item, sow as being more precise in it.

[newbie LAC]

 

9 hours ago, Midnight Modding said:

Sigh. I looked myself. I see it deletes them only for content items and just the way the code is (I haven't backtracked through the whole process), I get the feeling that $item really needs to be a content item?

See clubs

Content item?

No

Are notifications deleted when the club is deleted?

No

Bug?

Yes

Are notifications displayed when the club is deleted?

No

Do you see (get) any erros (whoops) on the notifications page when the club is deleted?

No

---

You can override as many methods as you want. Maybe you will create ips 5.0

[Midnight Modding]

Thanks. I think clubs is what I had seen when I made mine without content items, but I have spent so many hours on this, I keep forgetting things.

I have situations where the row isn't deleted, but the overall status changes and that is what complicates it. But I think I have it all figured out...

I know I can override, but the notifications page is not dieal to be overriding.

Either way, I am finallllly almost done.

[Midnight Modding]

Finally, I finished my TON of notifications and got them all showing up on the settings page and am done with the app except bug fixing and the upgrade routine and I think a couple tasks.

ps thanks @newbie LAC... I posted a reply to yours, but didn't quote you and everything is all out of order in here, due to it being a q&a.