Dreadknux

Last year, I re-organised my member usergroups to help protect from spammers and malicious users. The idea would be that, upon registration, a new user would be set in the usergroup 'Newbie', which requires their first 10 posts to be approved by mod/admin before being able to freely post as well as other restrictions (one of which being unable to make topics). These restrictions would be lifted when the user is promoted to another 'Regular User' group. I set up a rule for this ages ago with the following settings activated: Any Achievement Points Not Banned Groups: Newbie Member Joined: More than 60 Days Ago Last Posted: Anytime Last Visited: Anytime Actions: Move to Group: 'Regular User' However, I have just had a user complain that they registered back in Oct 2022 and still is unable to post topics. So I've had to manually 'promote' their usergroup. I checked the Member list in AdminCP and did a search for all users who had registered between Nov 1, 2022 and Dec 31, 2022 who were still in the 'Newbie' usergroup and to my surprise there were four pages of results! What am I doing wrong? These users should be automatically promoted but it clearly isn't doing that. The 'Enable Group Settings' toggle is ON in the Newbie group under 'Group Settings' in ACP as well. So it's not that. Is there a specific Task that isn't running properly here or something, that I need to look into? Any help is appreciated!

Yeah just to clarify/reinforce Randy's point in case it helps other people as well... you need to enable Push Notifications for EACH device you have in order for it to work. You can't just set it once on a desktop/mobile browser and expect it to work once the PWA is set up. I realised this myself when I had enabled push notifications on my community within the iOS Safari app (before I PWA'd it), but didn't get anything come through when I set up the PWA after. It treats the PWA as its own, separate "browser", so you will need to log in on the specific app instance, go to Settings > Notifications and scroll down to the bell to ensure that your PWA is specifically set up for push. Then it works. 🙂 I'm guessing this is some quirk with iOS, but figured I'd share just in case anyone else is pulling their hair out at this.

Hi guys, had a couple questions about the way the manifest settings work with certain browsers. 1. Desktop Safari in iOS seems to have broken the favicon to the point where it is just showing a white circle. My version is 16.3 running on mac os 12.6.3 if that helps (maybe it needs an update?). I've uploaded an image that has black vectors, but I also tried deleting that file and just having nothing set for 'Safari Mask Icon' and I'm still seeing just a white blank icon where the favicon should be in the bookmarks tab. 2. I uploaded a Maskable Icon (which features a circular logo for my site and a colour/image background) and while it seems to be used correctly for various areas on Safari and Chrome (as a bookmark or saved app), on Mobile iOS when I try to save the community to my iOS Home Screen (using Bookmarks > Add to Home Screen) the icon that presents itself is the one I have uploaded for Application Icon instead. Is this down to the iOS Home Screen/Push notifications thing being quite new? Is it possible to force iOS to accept the Maskable Icon if it is available, as using the Application Icon (which has a transparent background) does not look good on iOS Home Screen (it fills the transparent space with an ugly black colour). 3. I notice that in Chrome browser, it ignores the favicon uploaded to the Icons & Logos section and instead includes the Application Icon where available. Is there a way to force Desktop Chrome to accept the Favicon instead? When I set the Application Icon to match the Maskable Icon (i.e. having an image background) in an attempt to see if I could fix the iOS Home Screen issue above, instead Chrome just decided to adopt the Application Icon in the tab window - and I'd much prefer to use a basic logo with transparent background for Chrome browser desktop (using a background looks ugly). Thanks so much for your help!

I’ve just been trying out the Gallery app via the demo, and I’m very interested in it - I would like to use it as a shared media depository that multiple users can pull from when making posts/content. However it doesn’t look like this is currently possible. I’d like there to be an extra permissions column setting that allows for usergroups to ‘access’ all uploaded images within a gallery/album when creating a post or other content in Post Editor. Not just images the user uploads themselves, but ALL images uploaded to that specific gallery album by ALL users with upload/access rights. Please let me know if this is possible, it’s literally the only thing stopping me from investing in the Gallery app (well, that and the ability to add custom fields to Gallery albums but I can ask about that later).

Well in the UK it has been nothing but typical beautiful British weather: Honestly, it’s surprising to see summertime come around so fast over here. Thanks for the updates, Olivia, it’s appreciated!

This is unbelievably cool. Thank you Matt and IPS Team for this new feature (and thanks Apple In a way I guess). I’ll be honest, I wasn’t really sure what all the options in the Icons & Logos / Manifest were all about (and I don’t touch Android so it’s benefits would have been wasted on me) so I just left it all alone. This has given me an opportunity to look into this more and offer a way for our community to stay more connected. Having a Home Screen app definitely helps lessen the pressure when dealing with competition via other platforms like Twitter and Facebook. Thanks again!

Agreed! The way things are going with my community, the CMS/Pages content will likely be some of the most valuable we will have (with collaborative databases etc), would be great to have an extra layer of backup security for this app.

I recently created a record / news story that included a quotation in the headline (or record title in IPS Field terms). Something like the below: Person From Company Issuing “Notice” to All Users It turns out that, upon publish, the “ quote marks in the title are being printed in the URL slug. So the resulting URL would turn out like this: [site]/[database]/person-from-company-issuing-“notice”-to-all-users-rXX I think the same thing happens with single quote marks like ‘ as well. I don’t think this should be happening… I don’t have any screenshots to share on this I’m afraid, but also when I tried to fix the situation by editing the record in the front end and creating a custom URL slug (basically just the same thing but without the quote marks), the IPS Suite errored out on me. I can try to replicate this for you if you need me to, but hopefully this report is enough?

This would be nice to see in the core IPS framework but I wonder if this is something that @SoftwareFactory would be willing to include in their Brilliant Discord app as well?

Thanks a lot for the information @Matt, it's really appreciated. Just to beat the dead horse a little bit more, would the restoration of the two publish date concepts also allow for past date publish as well as future date publish? It's really less of an issue for me these days with this plugin I found, but I figure since I've been banging on about it for so long now I'm just curious. 🤠

I understand. Is this something that is going to be fixed? Maybe with the new Pages updates coming later this year? I don’t think it’s a satisfactory explanation, to simply leave the situation at this. Part of the IPS Suite’s selling point is to marry CMS content and forums, offering one complete unified community platform solution. If it turns out that the forum sync feature is not equipped to work properly with CMS/Pages after all, then I would say this is a major issue that needs resolving.

Thanks Marc - I’ve given up on the past dates issue, I’d like to switch focus to Future Dates now because this was present in the last version and now seems to have disappeared entirely. As @CheersnGears said, it’s an absolutely necessary feature of any CMS system and needs to return. Not sure what such a feature would negatively impact but I dare say it should be higher priority than other areas of the platform, if IPS wants Pages to be considered a serious CMS solution.

Decided to unmark my own solution and keep the topic open because of the above issue. While future posting doesn’t affect me too much at the moment (although it likely will later as I too work with embargoes) I think there is a problem here that needs addressing. I can fix my backdating issue with plugins but it might not be so easy for admins looking to publish stuff in the future. It’d be great to get some clarity on this, because IPS’ messaging over the last six months regarding the whole publish date issue hasn’t been clear or consistent.

Thought about this some more and it's not a huge issue for me so much anymore, as I found a plugin that allows me to change the publish date of a record: So the solution here is to install the above, set as 'hidden' any records I'm creating that I want to backdate, then use this plugin to change the record date before unhiding (it even changes the associated forum topic when using forum sync, which is perfect). That does exactly what I've been asking for this whole time, so no need to worry spending any more resources on publish dates in future versions now. Thanks!

Yes It is being synced with a forum.... why won't it work in this case? I feel like I'm going a little crazy here, I've been asking for a simple past-date function for my community for about 6 months and now instead entire feature has been pulled from my site. 😅 Is this something that will be worked on for a future release so it will work with forum sync?

The issue occurs in both situations - editing or creating. Both frontend and backend. Custom form template and default form template.

Field is set Setting not visible on default template CMS page Also in previous versions the date could be changed via ACP, under Publish Settings tab This is no longer the case.

Hi Jim - I see, so it's not an individual field. Any idea why the Publish Date field has disappeared from view then? Any and all options to set any publish date have vanished with this new version (this is true if using custom CMS templates, using IPS stock templates on the frontend as well as ACP, so I do not think it is a revised template bit issue)?

Hi guys Noticed this update in the latest 4.7.8 version: Eager to try this out, I updated my community to the latest version. But I cannot see where the option to set past dates lies. There's no extra field in Database > Fields page, there doesn't appear to be any such date setting in Database > Edit, and editing individual records (either on the frontend or via ACP) shows no date field options. In fact, where in the previous version there was the ability to set a future publish date on a per record basis, this setting also now seems to have disappeared! Have all these options been moved somewhere else, or have I got a bug on my hands?

I like to use the Events/Calendar app to mark upcoming release dates for games/movies etc. But it would be great if there was some kind of support for a product’s release date anniversary. At the moment, I can add an event specifically for a game’s past release anniversary (ie. “Release Date for Super Mario Bros on NES”) and state in the event description / event title that it is the game’s Xth Anniversary on that day. But I need to manually edit the event every year to update the details, and I’d rather that be automated in some way - especially if there are lots of event entries created for this purpose. Maybe it could take the form of a “show anniversaries” checkbox or something. But I think something like this would be super useful.

OK so small update, that 'record_image' code actually did work and it was just not showing up for me because of a cache issue. 😄 But I'd like to explore things further with this. 1. I'd still like to try and call custom fields within a streamitem 2. I'm trying to create an IF statement that would allow me to display something only if the streamItem entry is a certain content type (i.e. if this is a status update, then display this; if this is a 'news' database record, display that). I know the key to this is within the "$indexData['index_title']" but I can't seem to work out the correct parameters to accomplish the above tasks. Anyone have any ideas?

Hey all, trying to customise the activity stream a little bit and coming into some roadblocks. The templates for these aren't as accessible as some of the others in the IP suite 😅 I'm digging into the core > front > widgets > streamItem template right now, and redesigning as I see fit... I'd like to be able to include a record image (or in some cases, a custom field) in the stream snippet if the type of content is something specific (i.e. a record image for a record posted in a 'news' database, and a custom field [image] for a record posted in a different database). How would I go about calling the fields for these? I tried something like this, to test: {{if $itemData['record_image']}} <p>Yes</p> {{else}} <p>No</p> {{endif}} But it doesn't seem to work (just outputs 'No' regardless, so I'm assuming it's not successfully calling the record image field for the stream item). Any ideas?

Haha! Just my luck! Thanks Daniel, appreciate the assistance!

Hooray! Thank you! Much appreciated.

OK no problem, the backtrace info (with url removed): #0 [url removed]/web/system/Application/Application.php(236): IPS\Patterns\_ActiveRecord::load() #1 [url removed]/web/applications/core/sources/Achievements/Rule.php(107): IPS\_Application::load() #2 [url removed]/web/system/Theme/Theme.php(885) : eval()'d code(1397): IPS\core\Achievements\_Rule->extension() #3 [url removed]/web/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_admin_achievements->rulesListRows() #4 [url removed]/web/system/Theme/Theme.php(885) : eval()'d code(1354): IPS\Theme\_SandboxedTemplate->__call() #5 [url removed]/web/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_admin_achievements->rulesList() #6 [url removed]/web/applications/core/modules/admin/achievements/rules.php(94): IPS\Theme\_SandboxedTemplate->__call() #7 [url removed]/web/system/Dispatcher/Controller.php(118): IPS\core\modules\admin\achievements\_rules->manage() #8 [url removed]/web/system/Node/Controller.php(69): IPS\Dispatcher\_Controller->execute() #9 [url removed]/web/applications/core/modules/admin/achievements/rules.php(45): IPS\Node\_Controller->execute() #10 [url removed]/web/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\achievements\_rules->execute() #11 [url removed]/web/admin/index.php(13): IPS\_Dispatcher->run() #12 {main} Loaded hooks, in case it's relevant: applications/brilliantclipboard/hooks/StandardDispatcherHook.php applications/axenfontawesome6/hooks/loadJSandCSS.php applications/brilliantdiscord/hooks/standardDispatcherCss.php applications/brilliantdiscord/hooks/member.php applications/fxpages/hooks/constructFromData.php plugins/themeusagecounter/hooks/theme.php applications/brilliantdiscord/hooks/group.php Does this help?