Dreadknux

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?

Hoooooold on @Matt I was told that setting past dates on Pages wasn't happening anymore after my own bug report here. I just bought a plugin to sort the issue out for me 😅 Am I right in assuming that with the March update, we can set past dates on already-published records as well as set past dates on new records being created? I just want to make triple-sure so I know, because I've been so confused these past couple weeks! 😄

Actually, yeah now that you mention it. There's a bunch of "OutOfRangeException:0" errors logged (probably the same number of errors as when I tried to load the page). Is it safe for me to post the backtrace details of this log here, or do you not need any more info?

Hello IPS team! I just saw this strange notice on my ACP when looking through my Achievements Rules list: It doesn't relate to any theme template bit that I can manually restore, as the template referred to is in the /admin/ folder (which isn't visible when editing a theme's HTML/CSS - I certainly can't find the "rulesListRows" template when searching for it). I'm not sure how this happened either because I don't recall seeing a template called "rulesListRows", much less editing it. The direction to "run the support tool in the AdminCP to restore the default theme" is pretty vague as well. I'm not sure where I'm supposed to go or what I'm supposed to do to action this (I assumed it was go to Themes > Edit CSS/HTML > Restore template bit, but as I mentioned above this template doesn't isn't accessible in that part of AdminCP). Any ideas on how to fix? And this won't do anything to mess up my existing theme, will it? I'm assuming not, seeings as it references an ACP template bit, but I wanted to make sure.

Sorry to revive a dead thread, but I wanted to see if this suggestion was being taken on board? I think having more options for formatting the datetime parameter would be great on the theming level. For example, I might want a datetime on profiles only to read as: Aug 31, 2022 With short month names. Which I can't do at present with the current boolean options. Is it possible to add a ' format="m/j/Y" ' parameter to allow for a full suite of date and time options, as Morrigan suggests in the OP?

My community has been asking for a means to toggle/collapse widgets, in the same way you can for forum lists. Is there a way you can do this already, or is it something that IPS needs to add to the system? I noticed an old plugin on the Marketplace that seemed to accomplish this: But it doesn't seem to be downloadable anymore, or compatible with the latest version.

I just wanted to let you all know that I had a good night's sleep and I'm over it 😅 Many thanks to Stuart, Marc and Matt for assisting with all of this, and for the feedback/context. I think the important thing as a customer is just knowing if your feedback is being heard or not, and it was a little bit confusing to think that was happening within this particular thread. I apologise for getting the wrong end of the stick here. I'm glad to know that use cases are being considered for future updates. I'm more than happy to serve myself up as a guinea pig and road test whatever swanky rewrite you have cooking if it will help to get some added perspective! 🙂 For now, I'm going to look into this plugin that was shared earlier and hope that all my previous suggestions relating to Pages/CMS are being considered as I think that would really help make IPS shine in future versions.