Kentico Creating Page based on existing Page Type gives error - kentico

and thank you. I am following the Kentico 13 tutorial and I am facing the next error when I am trying to create a new page based on a page type that has page builder available:
"An error occurred while attempting to retrieve page templates. Contact your system administrator and check that the page builder feature is registered correctly in the MVC project."
I have registered page builder by doing features.UsePageBuilder() in the configuration of the project so I am not sure what I have wrong here. Thank you again if someone can help

Have you tried the suggestions from this thread on the same error?

Related

Email Attachments to SharePoint Document Library - Error

I have this weird problem when I try to use a simple default flow template to save email attachments to the company main SharePoint site: company.sharepoint.com (not subsite).
So I get started, by taking all the defaults of this flow, however, once i get to the point of providing the site address and document library path I get the error highlighted in red.
Where I get confused is that when I create a subsite like company.sharepoint.com/sites/testsite I enter the subsite address and the folder path automatically populates the folder structure for me to pick where I want to save such attachment.
I have given full owner permission to this test account with same results. So permission is not the problem.
My question is, could it be I'm using the wrong flow to save to a main SharePoint site? or this is something not allowed?
You could check the connector and recreate a new connection to SharePoint.
In many cases, an error code of 403 appears in a flow fail because of an authentication error. If you have this type of error, you can usually fix an authentication error by updating the connection, please make sure you have update the connection.
You could refer to this article.
Just in case anyone has a similar problem, the account to which you are creating a power automate flow must be a site collector to the root SharePoint site.

404 error being generated on controller actions that use [HttpGet] when clicking on a hyperlink?

Background
I have an ASP.Net Core v2.0 web application that has the [HttpGet] attribute above action results that don't need to accept a post.
I created a spreadsheet with a list of pages on the website to my marketing team, along with a column of hyperlinks that link directly to each page on the website.
Example Spreadsheet:
Issue
Once the marketing team started clicking on the links in the spreadsheet, I started to receive 404 errors via email (configured using NLog) although the page did still load for the user.
Troubleshooting
I troubleshooted this and uncovered that the issue was down to the [HttpGet] attribute. If I take the [HttpGet] attribute out, clicking on the links in the spreadsheet doesn't generate a 404 error.
The site doesn't generate 404 errors when loading the page (s) via the browser.
I installed fiddler and it looks as though Excel is using the "CONNECT" method.
Fiddler screenshot:
I thought this could be the issue as it's not a GET but when I access a page within Chrome, it also shows using the "CONNECT" method in fiddler.
I'm looking to see if anyone else has had this issue and if they got around it? Do I need to add another attribute alongside [HTTPGet] to stop Excel or other 3rd party software causing a 404?
I've resolved my own issue.
For anyone else that has this issue the fix is to put [HttpGet, HttpHead] as the attribute. If you have a custom route then add another attribute underneath:
[Route("[controller]/custom-action")].
For info, I got to the bottom of this by using the logs from the drop down ASP.Net Core Web Server in the output window in Visual Studio. I could see that when the link was first being requested by Excel, it was using the HEAD method rather than the GET which is why a 404 error was being fired.
Hope that helps someone down the line.

SuiteCommerce Advanced page error - Cannot read property "length" from null

I have some problems in E-Commerce website development through NetSuite. Am getting an error when I tried to go Setup -> SuiteCommerce Advanced -> Configuration page it displays below error. I think it is from user privilege issue may be.
I am new to NetSuite, please someone help me how can I get rid of this.
Thanks in advance.

Display error messages from j_exception on error page on unsuccessful login (JAAS - LoginException Handling)

Display custom error messages on unsucessful login using jaas's j_exception
I have configured tomcat to work with jaas to authenticate my users. I have made use of form based authentication and hence on unsuccessful login i navigate to an error page. Instead of an error page with static message, I wish to display appropriate messages like "Invalid username/password" or "User locked"(i lock the user after 5 unsuccessful attempts) etc from j_exception
How can i achieve this?
I tried googling around the issue and found the following link
http://www.jroller.com/heonkoo/entry/manipulating_login_exception
But this seems like an old post.
I have been struggling with this from a few days. Any help will be greatly appreciated.
JAAS does not provide a standard way to propagate information to the web layer.
You can use a ThreadLocal to store the exception and read it in your error page.

It is Possible to connect the site page with layout pages sharepoint 2010?

it is possible to connect the site pages with layout page in sharepoint 2010. I did but i got the problem when i am save the data ie Publish the page it will give me error follwoing error:
Error An unexpected error has
occurred.
Troubleshoot issues with Microsoft
SharePoint Foundation.
Correlation ID:
9bc41e28-4fe1-4b4f-9e00-0e0494ef9e6e
Date and Time: 7/1/2010 3:30:29 AM
Please any one have idea. Please solve my problem thanks Waiting for your response. thanks
Open the Log files in the 14\Logs folder and search for the Correlation ID: 9bc41e28-4fe1-4b4f-9e00-0e0494ef9e6e . You should get more specific error information that will help to dig deep in to the issue.
Also try to enable CustomError=Off & CallStack="True" in the Web.config file.

Resources