I would like to hide the 'Status Button' that allows customers to reopen or change the ticket status in the Customer Portal Ticket detail view.

I found the CSS file responsible for this however when I make changes to this file they are not applied.  I have rebuilt and deployed the application but it is like it does not even see my changes. 

CSS file location:

C:\Devel\ProdVFS\Model\Portal\SLXCustomerPortal\SupportFiles\css\sage-styles.css

The class is .sxlbutton.  I attempted to change the display to: display: none to hide the button.  However when I do an inspect element the default display: inline-block is still being applied.

Any ideas or tricks of how to apply a CSS file?  Shouldn’t a complete rebuild and deploy of the portals push out this change?  Am I missing something else?

Okay so I guess I never noticed this before...

Application Architect has two 'rebuild' options.  Build 'Web Platform' and 'Build Interfaces'.  In the past I always did the crtl build rebuild Web Platform and did not notice the interface botton until hovering over buttons today.  By rebuilding the interface button CSS or other code changes in the portal pushed down.  Then release the portal as normal.

Simply change the .slxbutton CSS proptery to display: none;

Hope this helps someone in the future.

Jacob:

  Not sure of exactly why your changes were not taking, but just to expand a bit on what you are doing:

  - Build Interfaces is a Partial Build of only components that are Data Related (e.g. Entities and Relationships). You do this within App Architect so that your Entity Changes are available when coding.

  - Build Web Platform is a full build, and will include a Build Interfaces

  - Hoding the Control key while Executing a Build does a "Rebuild". A Rebuild will Clean the Target and Make sure all the files generated are new. Otherwise the system only builds the areas that it has marked as having pending changes.

  - Now, not all the Items are touched by the Build (or Rebuild) Process. Most Items that are added into the Support Files folder are just copied AS IS during Deployment (exception would be Javascripts that are minified). Most CSS files are just located under the Support Files folder (within the CSS subfolder) and as such are just copied onto the Deployment folder.

Now, when doing a Deployment, I have found out that it does compare files by Date, so if you have made changes on your files on the Target site, it will not overwrite them during Deployment if the files have modified since (I believe that I have seen this behavior change among different versions)