cms_site | Lift CMS site | Content Management System library
kandi X-RAY | cms_site Summary
kandi X-RAY | cms_site Summary
The Lift CMS site is statically generated on push using and lives at . The underlying engine behind Telegram is the hoisted static site generator, which is built on top of Lift itself.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cms_site
cms_site Key Features
cms_site Examples and Code Snippets
Community Discussions
Trending Discussions on cms_site
QUESTION
I created a dev instance of my Kentico sites from a copy of my staging instance. I changed all the site display names in the Sites admin module to denote that these were now all the dev sites instead of staging ones and it broke all my sites by setting the SiteDefaultStyleheetID and SiteDefaultEditorStylesheet columns to NULL on the CMS_Site table for each renamed site.
To be clear, I did not mess with any site code names when I did this. They all stayed the same. I also created this dev instance by copying the entire file system (7-zipped) and db (created a .bak file) from the staging server to a dev server. I didn't do any export or importing of sites to create this dev instance.
What's more, the "Site CSS stylesheet:" and "Editor CSS stylesheet:" dropdown menus don't display any of the stylesheets assigned to the renamed sites. However, when I check to see if any stylesheets are assigned to those sites under "Assigned Objects", all the appropriate stylesheets show up as assigned to their proper site.
If I brute force the default stylesheet IDs back onto the Site records in SQL, the sites will display properly, but the "Site CSS stylesheet:" and "Editor CSS stylesheet:" dropdown menus ins Sites will remain empty. Also, If I edit the site display names again, the default stylesheet columns get reset to NULL.
Does anyone know if this is intended behavior? Has anyone encountered this before, and if so, how did you remedy the problem?
It looks suspiciously like a bug for such an important part of a site such as a default stylesheet to break simply because the site's display name changed while the integer ID, GUID, and code name all remained the same.
...ANSWER
Answered 2018-Dec-17 at 20:44If you look at the documentation you'll see the setup with files and folders specific to CSS and Themes. They are specific to the sites code name. If you change it, this will break the URL path Kentico looks for automatically. If you want to define the site for each environment, I'd suggest simply updating the display name and not the code name. Honestly, there's no reason to change the code name, except to make more work for yourself.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cms_site
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page