CODEWITHSUNDEEP
c#asp.net
Break
Break

Reputation: 51

content placeholders pages not showing inside master page

I'a currently working on C# aspx.net project, and all of a sudden the pages that should load inside master page are not shown, it's like "hidden", only master page is showing, i didn't do nothing revelant to it, i think. It's getting me insane because i already loaded a backup that i got, and the same problem occurs. So maybe i did something wrong to my Visual Studio 2019? Does that ever happened to anyone? I've tryed to change the Netframework from 4.5 to 4.6 but the problem persists. if i inspect the page on google devtools, the page's are there, but not showing on the content placehonder.

Example of my master page:

<%@ Master Language="C#" AutoEventWireup="false" CodeBehind="Masterpage.Master.cs" Inherits="WORKFLOW_FACTURE.Site1" %>
<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
....
<asp:ContentPlaceHolder ID="head" runat="server">
    </asp:ContentPlaceHolder>
</head>
<body>

<div id="wrapper">
    </div>

<div id="page-wrapper">

    <asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">
    </asp:ContentPlaceHolder>

</div>
<!-- /#page-wrapper -->

</body>
</html>

example of one page that should be loaded whenthe user enter the masterpage:

<%@ Page Title="" EnableEventValidation="false" Language="C#" AutoEventWireup="false" MasterPageFile="~/Masterpage.Master" CodeBehind="Indicateurs.aspx.cs" Inherits="WORKFLOW_FACTURE.Indicateurs" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">
<form runat="server">
....
</form>
<script type="text/javascript">
...
    </script>
</asp:Content>

Upvotes: 1

Views: 623

Answers (1)

Bruno
Bruno

Reputation: 432

I alredy had that same problem on my asp.net application, where bootstrap classes weren't recognized. It can happen for two main reasons:

1 - *the links *.css / script .js are being called from the master page at bad order, and because of that, dind't load properly.

2 - Calling bootstrap.css instead of bootstrap.min.css, that happened to me, i think that's because of the load time that can be relevant to the content page.

Upvotes: 1

Related Questions