2,450 reputation
2723
bio website
location Germany
age
visits member for 3 years, 2 months
seen 22 mins ago

Have been working with SharePoint since Tahoe Beta 2 (SharePoint Server 2001).

SharePoint aficionado with a dedication to user experience, usability & accessibility and branding & Web design.

Loving SharePoint GUI customization & tweaking and enhancing built-in functionality.

Strong dedication to cross browser/device/operating system support when architecting & building SharePoint solutions.


Mar
5
answered Deny user access from SharePoint Native but allow it from custom application
Mar
5
revised Editing OOB “Add Comment” Post Webpart
added 70 characters in body
Mar
5
revised Editing OOB “Add Comment” Post Webpart
added 785 characters in body
Mar
5
comment Editing OOB “Add Comment” Post Webpart
Again, it depends on what you want to style. But for simple CSS you can add a Content Editor WebPart to the post.aspx page, make it hidden and add you CSS in there. Neither SPD nor masterpage changes are required for such a task.
Mar
5
comment Editing OOB “Add Comment” Post Webpart
Sorry, unfortunately I am not a magical SharePoint master, hence I don't know how to avoid that DataFormWebPart issue you are facing.
Mar
5
comment Editing OOB “Add Comment” Post Webpart
To use SPD to insert a new "Add Comment" WebPart you need to open the post.aspx page directly and insert it there. This should work (kind of) but I never tried it myself for the reasons I mentioned already.
Mar
5
comment Editing OOB “Add Comment” Post Webpart
The biult-in SharePoint input forms don't use XSL but rather are implemented as server-side ASCX WebControl rendering templates, living in the ControlTemplate folder on the server. Changing them is possible but requires at least ASP.NET knowledge and advanced SharePoint knowledge if you want to change them globally for all Blogs on your SharePoint farm. Modifying them with SPD (by converting to XSL) can have a gazillion of unwanted side-effects hence I personally don't recommend doing so. But others might have a different point of view...
Mar
5
comment Editing OOB “Add Comment” Post Webpart
I've updated my post to give you some more pointers.
Mar
5
revised Editing OOB “Add Comment” Post Webpart
added 271 characters in body
Mar
5
comment Editing OOB “Add Comment” Post Webpart
Styling text is a pure CSS task and could even be done with Notepad (although I prefer the free and opensource Notepad++). Reordering fields can be accomplished on the list settings page of the Comments list without SPD.
Mar
5
revised Editing OOB “Add Comment” Post Webpart
added 218 characters in body
Mar
5
comment Editing OOB “Add Comment” Post Webpart
It sounds like you are trying to use SharePoint Designer (SPD) to customize your blog. My general advise is to stay away from SPD for such tasks like changing Blog pages and WebParts and use it only for masterpage, CSS and JavaScript related modifications. Everything going beyond those tasks you'd better moving to C# and custom coding in Visual Studio. But again, it really depends on what exactly you want to accomplish beside of hiding a field.
Mar
5
comment Editing OOB “Add Comment” Post Webpart
You don't need to touch NewComment.aspx as it is an internal page not used when a user wants to add a comment to an existing post, you also don't need to create a new aspx page. Please update your original post with more details hat you want to style and check the MSDN documentation on the SharePoint object model and PowerShell how to mark fields hidden.
Mar
5
revised Editing OOB “Add Comment” Post Webpart
added 175 characters in body
Mar
5
answered Editing OOB “Add Comment” Post Webpart
Mar
5
answered ContentPlaceHolder generates automatically width=100%
Mar
2
comment Hiding left hand navigation menu
How did you apply the CSS code?
Feb
17
revised How to make Grouped View work with the $(document).ready event?
added 628 characters in body
Feb
17
revised How to make Grouped View work with the $(document).ready event?
added 76 characters in body
Feb
17
revised How to make Grouped View work with the $(document).ready event?
added 523 characters in body