DOJO error?
Do you get any errors in Console or EPi log file?

Hm, I managed to reproduce the same behaviour.
If your page inherits ContainerPage but you don't create a controller for your page type, 'All Properties' button won't be displayed.

Is that the case?

The only thing i get is 

NetworkError: 404 Not Found - http://myverysecretlocaladress/ClientResources/Styles/Styles.css

It inherits PageData. The thing it that it worked before... 

Can you set a break point in controller?
I guess that DOJO error will just make the 'All properties' button unclickable (loading animation that never stops), but it won't hide it.
So I vote for controllers :)

Controller created and the "All properties" button is visible, but for some reason I still can't load the all properties view.... .

Can you send a code snippet or your page class and controller?

Thanks

[ContentType(
GUID = "D8C04E85-0C31-494C-88E1-54CC16017C7E",
DisplayName = "Settings page 2",
Description = "Page used for site settings",
GroupName = "Platekompaniet"
)]
public class SettingsPage : PageData
{
[Display(
Name = "Topbar settings",
Description = "Settings for the top bar on the page",
GroupName = CustomTabNames.HeaderSettings,
Order = 10)]
public virtual TopBarSettingsBlock TopMenuSettings { get; set; }

[Display(
Name = "Header settings",
Description = "Header settings",
GroupName = CustomTabNames.HeaderSettings,
Order = 20)]
public virtual HeaderSettingsBlock HeaderSettings { get; set; }

[Display(
Name = "Variant page settings",
Description = "Variant page settings",
GroupName = CustomTabNames.VariantPageSettings,
Order = 30)]
public virtual VariantPageSettingsBlock VariantPageSettings { get; set; }

[Display(
Name = "Page references",
Description = "",
GroupName = CustomTabNames.PageReferenceSettings,
Order = 40)]
public virtual ContentReference TopCategoryFolder { get; set; }

and

public class SettingsPageController : PageController<SettingsPage>
{
public ActionResult Index(SettingsPage currentPage)
{
return Content("");
}
}

Thank you for your help, very appriciated! :)

[ContentType(
GUID = "D8C04E85-0C31-494C-88E1-54CC16017C7E",
DisplayName = "Settings page 2",
Description = "Page used for site settings",
GroupName = "Platekompaniet"
)]
public class SettingsPage : PageData
{
[Display(
Name = "Topbar settings",
Description = "Settings for the top bar on the page",
GroupName = CustomTabNames.HeaderSettings,
Order = 10)]
public virtual TopBarSettingsBlock TopMenuSettings { get; set; }

[Display(
Name = "Header settings",
Description = "Header settings",
GroupName = CustomTabNames.HeaderSettings,
Order = 20)]
public virtual HeaderSettingsBlock HeaderSettings { get; set; }

[Display(
Name = "Variant page settings",
Description = "Variant page settings",
GroupName = CustomTabNames.VariantPageSettings,
Order = 30)]
public virtual VariantPageSettingsBlock VariantPageSettings { get; set; }

[Display(
Name = "Page references",
Description = "",
GroupName = CustomTabNames.PageReferenceSettings,
Order = 40)]
public virtual ContentReference TopCategoryFolder { get; set; }

and

public class SettingsPageController : PageController<SettingsPage>
{
public ActionResult Index(SettingsPage currentPage)
{
return Content("");
}
}

Thank you for your help, very appriciated! :)

I've imported SettingsPage and SettingsPageController in AlloyTech website and everything works fine :(

I know that this is not an answer to your question, but can you:

1. Create a new tab on start page and set a restriction so that only administrators can open that tab
2. Move all the properties from SettingsPage to StartPage (inside that "special tab")

You then don't need a SettingsPage, because your site settings are easily accessible:

var contentLoader = ServiceLocator.Current.GetInstance<IContentLoader>();
var startPage = contentLoader.Get<StartPage>(ContentReference.StartPage);
            
// do something with startPage.TopMenuSettings
// do something with startPage.HeaderSettings

Seems like a proper solution. Thanks for your input!

A colleauge of mine removed a property that was not in use. For some reason it now works.