kgiszewski / learnumbraco7 Goto Github PK

The author wrote...

• Create a Site document type (or whatever you name it) that will reside on root of your content section for each of your sites.
• Use relative paths when using data types such as the multinode tree picker.
• Create a Home page under your Site node and all pages as children under the Home node.
• Assign a domain to each Home node.
• Consider creating a Site Settings document type to hold settings for each website.

My questions based on bullets above:

• Do we need to create a Site template along with the Site document type? or just have the document type itself?
• RenderBody(), does not work on a Site template. It belongs to a Master template. So do I need to create an additional Master template?
• Where do we write relative paths with the Multinode tree picker? Show me an example of where a relative path should be written.
• Before we get to the part of having a home page, do we need to create a Home document type with Home template? and then make this Home template a child of the Site template?

I apologize if this sounds like 1st grade Umbraco questions - I just want to make sure I'm on the same page.

Thanks!

Maybe copy your stuff into these chapters?

Write How to organize Visual Studio 2013 Solution to create Umbraco addons

I've personally been out of the day to day Umbraco game for about a year now. So if anyone wants to contribute to this e-book. Please send up a PR.

Be sure to include yourself in the author section :)

This is a general solicitation for any contributors. Don't be shy and don't worry if you think you can write an already written section, better.

Fork this repo and send a PR please :)

Hi again,

Maybe you could make a danish branch I could send the pull request to ?

Thanks

The problem here is it's difficult to determine the 'right' way as the official docs sort of meander between the 'old' way and the 'new' way.

Make it easier to go page to page

It seems GitHub changed their markdown rendering algorithm and no longer recognizes the particular headers used in this repo.

I'll be addressing this issue shortly. Just wanted to create an issue before creating the pull request to follow what I suspect is the correct process.

There are great reasons to create a Site Settings Container in the way you have under a Domain Node but I get a lot of mileage out of having a Site Settings Tab on the Site Node and using recursive property calls in the razor files. This isn't clear from the notes and IMHO we are educating people on best practice so hopefully my idea of this as a best practice is ok. I know it might be slightly off topic but do you think it is valuable to show Site Settings Tab and Site Settings Nodes in the images.
https://github.com/kgiszewski/LearnUmbraco7/tree/master/Chapter%2012%20-%20Multisite%20Configuration

You have a page on surface controllers here: https://github.com/kgiszewski/LearnUmbraco7/blob/master/Chapter%2006%20-%20Surface,%20WebAPI%20and%20RenderMVC%20Controllers/02%20-%20Surface%20Controllers.md

Something that can confuse people who know MVC is that surface controllers can use a hidden input field with a name of "ufprt" to perform some routing (rather than use the URL). You can see that in action here: https://github.com/umbraco/Umbraco-CMS/blob/release-7.3.4/src/Umbraco.Web/Mvc/RenderRouteHandler.cs#L138

Basically, that value contains the controller/action (and some other route info) and Umbraco routes using that data rather than the URL (though, it seems a particular URL also does work).

Since this may trip up many people, including those already familiar with MVC (it tripped me up for a while), it seems like it would definitely be worth clarifying in your GitHub repo.

I think the "ufprt" value may also contain the current page ID, but I need to research that a bit more to confirm.

If I can find some time, I'll submit a pull request eventually for this. However, if you want to write this documentation in the meantime, feel free :-)

Hi Kevin,

I've started translating the files ... but I wondered if I should translate the names of the chapters, like

[Next> 01 - Developer Tools](01 - Developer Tools.md)

Because I don't know if you reference them somewhere, to the english names etc ?

//Thanks

Presently, if a book contains javascript a system will run it creating a XSS situation. Ideally I would like to make this possibility less likely than it is now.

Things I've tried:

• Using HtmlAgilityPack to remove script tags
  • This sort of works, but blows up all generics documentation GetPropertyValue<foo>("") and any literal < >
• Force entity encoding
  • Sort of works, but code tags need to be untouched (I think) as it leaves the entities in place
• Remove bad tags just before we render to the div
  • Not yet tried.

Strip headers/add misleading headers
Rewrite /umbraco to something else

This is the 1st party form section.

Use subfolders in views folder

@alindgren, feel free to edit your bio: https://github.com/kgiszewski/LearnUmbraco7/blob/master/Chapter%200/README.md

I'm not sure what is the full intent of http://24days.in, but

1. The site appears not to work
2. If you attempt to access the /umbraco backoffice area, it requires a username and password.

This link can be found on Chapter 01, 02-Community.md

The Error: Umbraco.Web.UmbracoContext.PublishedContentRequest.get returned null

The code:

public class CategoryController : RenderMvcController
    {
        //Basic Product
        public override ActionResult Index(RenderModel model)
        {
            LogHelper.Info<CategoryController>("Hello, we have a custom model in category.");
            return View(new CategoryModel());
        }        
    }

    public class CategoryModel : RenderModel
    {
        public List<ProductDetailsModel> categoryList;

        public CategoryModel()
            : base(UmbracoContext.Current.PublishedContentRequest.PublishedContent)
        {
            categoryList = NopCommerceService.Instance.GetNopProducts().Products;
        }
    }

Need to find someone to write the history :)

Use the Bookshelf example of adding file system files to an Examine index.

Hi, i just copyed your code under MyNameSurfaceController Class. So i hoped to route controller as you described : /umbraco/surface/mynamesurface/getnames But i get HTTP Error 404.0 - Not Found. I tried everything I could but no result. Umbraco version is 7.12.4. Anyone had same problem before ?