In previous posts, we learned how to create a module inside of ContentBox, and then we added a handler and view so we could view the module behind the security of the login, but having an admin module, without menu items, is fairly silly ( usually ). In this blog post, we'll learn how you can add Submenu items to existing menus, like the Modules Main Menu.
An incredibly powerful feature of ContentBox 3 is the increasing availability of open source themes to jump start your custom development. For those wishing to contribute back to the community, creating your own theme is as simple as cloning one of our boilerplate themes, creating a new GitHub repo for your customizations, and publishing your theme on Forgebox.
We are happy to announce, ContentBox 3.0 FINAL is now available to the public. After a lot of hard work, we are finally ready to cut the release. With 100+ issues included in this release, this major release is nothing short of massive. With ColdBox 4 updates, Theme updates, Enterprise updates, Security Updates, JSON Support and Exports, Native Markdown Support, Autosave and much more, this major release has something for everyone. ContentBox 3.1.0 is already in development as well and can be installed via CommandBox using the
Alongside the release we have many other announcements around the CMS. So get ready!
In our last post, we started building an Admin Module. This process isn't actually that difficult or long, but we have broken it into separate blog posts to make it easier to read each piece. We have built our basic ModuleConfig.cfc, now we need to build an event handler and view, so the default action when you hit your new module have something visible. Our module was called mySecrets, so lets move on.
In previous posts, we looked at how to extend ContentBox 3 with ColdBox Modules, installing from Forgebox with CommandBox, or creating your own. In this post, we're going to look at how you can create your own Admin Modules, add Menu Items into the Admin Interface, use ContentBox admin Users and Permissions instead of building your own security by extending ContentBox.
Friday, July 29th is the last of our webinars in our ContentBox Roadshow, which has been pumping out blog posts and webinars all throughout the month of July. In this last webinar I'm going to do a deep dive into modules, providing a walkthrough on how to create modules, and use them in your ContentBox site, hopefully that sounds interesting, and you'll join us.
ContentBox sports many out of the box comment moderation tools.
From the screenshot you can appreciate all the different tuning you can do for comment moderation:
- All comments moderated
- User must have an approved comment to be approved consequentely
- Auto-deletion of comments that are moderated
- Moderated keywords (ip addresses, authors, emails, or content)
- Blocked keywords (ip addresses, authors, emails, or content)
My favorite setting is the auto-deletion of moderated comments. I have never ever ever ever cleaned up spam anymore. I let ContentBox do it every X number of days and I truly appreciate that as it is one less thing to worry about.
Modules are one of the key components of everything ContentBox. Adding a module into ContentBox is fairly simple, we have a few blog posts already outlining some of the different ways you can create them, but we have left out one very important piece so far ( we actually had a few questions about it on the CFML Slack Channel ), how do we theme our custom module output? Theming your custom module, so it uses the same theme/layout as the rest of your ContentBox site is now a reality. This is vital if you are going to be extending your site with your own modules, and you would hate for your module to be tightly coupled to the current theme, making it harder to change themes. This could be difficult, but luckily for you, its simple.
ContentBox 3 is a big step forward for us, as we have discussed during our month long roadshow... and in todays technological state, we can't talk too much without mention Mobile apps. This Friday, July 22nd 2016, at 11 Central, Scott Steinbeck will be leading a webinar on ContentBox + Mobile, to give you an overview of how he designed the Into the Box app for our conference in St Paul MN in June, written with Ionic and ContentBox.
The purpose of the Global HTML manager is to allow the integration of third-party scripts, CSS or HTML integrations easily without altering code or programming it in the theme. This allows for cross-theme output in a manageable manager.