Databases
StackOverflow2013
Postsdbo
PO.NET MVC: How to implement different page appearance per user?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO.NET MVC: How to implement different page appearance per user?
    primarykey
    data
    text
    <p>I am running out of ideas here. Maybe you can advice me what pattern or method(s) to use.</p> <p>User should be able to log in and change the <strong>appearance only</strong> for his/her profile. The difference (AFAIK) with personalization is that personalized layout are seen only for the editor (him-/herself). The difference between skinning, I guess, is that Skins are predefined but users should be able to change the settings themselves.</p> <p>I need to be able to display the customized layout to everyone who visit author`s page.</p> <p>The good solution would be to keep the layout info in a DB table. Also it should be cached I guess to take load off the DB and used in CSS.</p> <p>Thanks</p> <p><strong>Edit:</strong></p> <p>OK I have done some research now. Came up with this kind of idea.</p> <p>In a View get a userId (Guid type) from a DB and set it to the ViewData: ViewData["userId"] = profile.userId;</p> <p>That View uses the following MasterPage called 'Profile.Master' and links to the dynamic CSS file:</p> <pre><code> &lt;link href="&lt;%= Url.Action("Style", "Profile", ViewData["userId"]) %&gt;" rel="stylesheet" type="text/css" /&gt; &lt;/head&gt; </code></pre> <p>In the ProfileController get the CSS data from DB and return it to the dynamic CSS View:</p> <pre><code>public ActionResult Style(Guid userId) { var styles = (from s in Db.UserStyleSet.OfType&lt;UserStyle&gt;() where s.aspnet_Users.UserId == userId select s); return View("Style", styles); } </code></pre> <p>The problem is that the UserId is never passed to the dynamic CSS link:</p> <p>The parameters dictionary contains a null entry for parameter 'userId' of non-nullable type 'System.Guid' for method 'System.Web.Mvc.ActionResult Style(System.Guid)' in 'Project.Controllers.ProfileController'.</p> <p>Any advice is welcome, thank you.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJ Pollack
    1. USJ Pollack
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO.NET MVC: How to implement different page appearance per user?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO.NET MVC: How to implement different page appearance per user?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO.NET MVC: How to implement different page appearance per user?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSounds to me like you already know the path to take...store the customization data in the DB.
      singulars
      1. PO.NET MVC: How to implement different page appearance per user?
      1. USJustin Niessner
    2. COalso see http://stackoverflow.com/questions/769878/asp-net-mvc-themes-how-to
      singulars
      1. PO.NET MVC: How to implement different page appearance per user?
      1. USMauricio Scheffer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload