Developer forum

In the template, you can add a check (if it is a Razor template) and return 404 if the paragraph is not active.

Otherwise we need to fix it in item publisher.

if (!Dynamicweb.Content.Paragraph.GetParagraphById(123).ShowParagraph) {
    HttpContext.Current.Response.StatusCode = 404;
    HttpContext.Current.Response.End();
}

Hi Nicolai,
If I use that code on my Item Details template (with modified ParagraphId) I get an error:

The name 'HttpContext' does not exist in the current context

Am I wrong to use it on the Details Template?

+ I think this would be something for future fixing in ItemPublisher... Right now I need to recode a quite large template ;-)

System.Web.HttpContext you need to write!

Ok, so redirect works – BUT how in the "beep" do I get the paragraphID of the item being published? I'm on a details view of a paragraph item being published?

Trying to set the paragraph ID as a variable to use in the IF you wrote...

In the dark here, can't wrap my head around getting that paragraph id to check if is supposed to be "ShowParagraph" or not...

It should be in the tag ItemPublisher:Item.DetailsUrl.PID.

The friendly URL is also rewritten to querystring parameters where you can find the information. You can see here: http://templates.dynamicweb.com/TemplateTags/Dynamicweb-template-tags/Module-tags/Item-publisher/Details/ItemPublisherItem-DetailsUrl-PID.aspx

Hmm... the PID is the ID of the paragraph on which the ItemPublisher is attached, not the ID of the original paragraph item...

The paragraph items are placed in the sitetree as so:

Department1  (page with item publisher attached to module)

AvailableJobs
--- Department1 (page with all the available jobs created as paragraph items - It is here the editor makes the differents jobs inactive, which removes them from the published list, but not from being able to visit them from the google index. Allthough there is already a filter to exclude all jobs where the Boolean "ActiveJob" is false from being published, and it works fine, but there is so many editors comming and going, and the client want the system to be able to handle "Include/Exclude" and return a 404 or go to the published list with a 301, which this code will do as soon as I can get a hand on the ParagraphID from the item being published.)

Note: there is no way to create any of the items as page items, this is a running solution with thousands of items.
 

Hi Nicolai,

Did you see my last post? :-)

Anyone?

Again... ANYONE?!

Okay, so I have done the below, and it works - BUT are there any large performance issues doing it this way?
It is used on a details view in ItemPublisher...

@{
    var theItemID = GetString("ItemPublisher:Item.Field.Id");
    var sql = "SELECT ParagraphShowParagraph FROM Paragraph WHERE ParagraphItemId = @theItemID";
 
    var currentPublishedItemParagraphVisibility = true;
    
    using (var cmd = Dynamicweb.Database.CreateConnection().CreateCommand())
    {
        cmd.CommandText = sql;
        Dynamicweb.Database.AddStringParam(cmd, "theItemID", theItemID);
        using (var reader = cmd.ExecuteReader())
        {
            while (reader.Read())
            {
                currentPublishedItemParagraphVisibility = (bool)reader["ParagraphShowParagraph"];
            }
        }
    }

    if (!currentPublishedItemParagraphVisibility) {
        HttpContext.Current.Response.StatusCode = 404;
        HttpContext.Current.Response.End();
    }

}

Nope, and it should only be reached by Google who will no longer index it and forget about it, so it will not have that big impact.

Ok,

Well, all active published paragraph items will use the same template on the details view, so it will be reached quite a few times a day... ;-)