Blog Bug.

Adam Jackman-Moore asked on September 11, 2014 08:17

Not sure if this is a bug, i doubt it as others would of complained before me.

I have gone to add a new page of type blog to my site. I have entered the name and description and it throws an error. See image below.

Am i doing something wrong?

Image Text

Recent Answers


Adam Jackman-Moore answered on September 11, 2014 08:18

Oh i should mention this is version 8.1 with the latest hotfix 8.1.2 applied.

0 votesVote for this answer Mark as a Correct answer

Moiz Mala answered on September 11, 2014 11:59

Hi Adam,

Can you please provide what did you selected as page template for Blog before you got the above screen?

As i tried choosing Page Template as Blog and it worked in 8.0.19 version.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on September 11, 2014 16:23

Do you have a space after the blog name? I've found sometimes the invisible space causes problems, especially when the name is used as the document name and eventually creates the URL.

0 votesVote for this answer Mark as a Correct answer

Adam Jackman-Moore answered on September 12, 2014 02:23

Moiz the page type is Blog and there are no spaces before or after, I tried all sorts of combinations. I think something is fundamentally flawed with this installation as I cannot do the same thing when trying to add a javascript reference with the javascript web part.

One thing I have noticed is that my main page template is not a master template. No idea how i did this or how to get it back to a master template. Could this cause these weird issues?

Image Text

0 votesVote for this answer Mark as a Correct answer

Adam Jackman-Moore answered on September 12, 2014 02:36

Support asked me to check my Event Log... i have some funky error message about permissions in here.

Description: Security check of the expression 'Rule("!CurrentUser.CheckPrivilegeLevel(UserPrivilegeLevelEnum.GlobalAdmin);", "does not have!0select operationtext0GlobalAdminGlobalAdmin0select leveltext1")|(user)administrator|(hash)45f78916e16326feac9a5eee9e04bb27e1872cffab4700b5e9c7472e42488ec3' didn't pass. The expression was signed by user 'administrator'. Remove the signature and re-save the expression by a user with proper permissions.

This site was exported from my local machine then imported to the staging server, did something not come across maybe?

0 votesVote for this answer Mark as a Correct answer

Adam Jackman-Moore answered on September 12, 2014 03:17

Ok fixed it myself surprisingly, still don't fully understand what the problem was. But followed this and now it works. https://docs.kentico.com/display/K8/Working+with+macro+signatures

1 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on September 12, 2014 14:01

Macros have signatures for security reasons. Creating macros is great and a powerful tool in Kentico. Problem is it opens a lot of holes for security issues which is why they have signatures. When each macro is they use a hash key which in v8 is now a web.config key. In v7 and earlier they used the connection string which changed from environment to environment (dev, staging, prod). When you change the hash key, the signatures become invalid and need to be resigned, which is what you did.

You may not have even used a macro but there are macros used all throughout the site that you may not even know about, especially while working in the UI. If you haven't read up on macros, I'd suggest using the page Kentico provided and check them out.

0 votesVote for this answer Mark as a Correct answer

Adam Jackman-Moore answered on September 15, 2014 11:14

Yup read up on them, found it frustrating I didn't see anything about this crucial step when exporting and importing from dev to staging however.

Kentico support however told me if i put this in the web.config for both dev and staging that i wont need to do it if it is the same key.

Obviously the value is what you have in dev already.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.