The Sitefinity SystemManager is a helper class that simplifies working within the Sitefinity system. Although it supports several advanced operations (such as loading configuration settings, registering web services, etc.) one of it’s most helpful features is the ability to report the current environment in which your code is executing. This is done through several helpful […]
Category: API
Today’s quick post just serves as a bookmark for a few helpful tools that I’ve used in the past to troubleshoot and debug GET and POST requests. Turns out I needed to use one again and I couldn’t remember what it was called or where to find it!
Sitefinity allows you to easily add simple custom fields to Content items using the backend administration, using the built-in field controls such as TextField. But what happens when you want to add a custom type and a custom field selector? The built-in custom field interface only allows a limited selection of field types, and the […]
If you are working with the Sitefinity Pages API you can easily retrieve the Id of any page in the system. You might also be working with a custom or intra-site module, which has a static Guid property for the landing page. The Page object itself only has a UrlName property, which returns only the […]
When adding controls to a Sitefinity page programmatically, by default it’s going to set restricted permissions so that only users in the Administrators role can view them. You can easily change this so that the widget is installed with the default permissions it would get by being dragged onto the page with the following code: […]
When developing a Sitefinity Intra-Site Module you’ll likely be creating public widgets that your users will be dropping onto pages. Rather than relying on your users to manually add them to the toolbox, you can register these controls yourself during module installation. Here is a demo code snippet that shows an example of how you […]
When migrating to the latest Sitefinity from the old version 3.7, by default the original .aspx page extension remains intact. It is stored in the Extension property of the PageNode. You can remove (or change) this extension with this simple code snippet: RemoveSitefinityPageExtensions.cs on Gist