MWS Login Page broken after Fix installation

after installation of MWS_9.7_Fix12, the MWS login page is broken(CSS style and CSS class references changed). Last known good MWS fix was MWS_9.7_Fix7.

I am also not able to access these CSS classes to make any changes to them.

Hi Anand,

is this really the css or is it just a wrong order of skin rules?

Are you still able to login to the instance or not?

If login is still working you can try to login as sysadmin and check the skin rule evaluation order.

Is there any thing the full.log of the MWS indicating issues during startup which might cause the effect you have described?

Please provide a screenshot of the login page for better understanding.

Regards,
Holger

Hello Herr. Holger,

I have similar implementation on various servers. All other servers are running fine.
The moment I installed this fix on my machine MWS Login page CSS style got changed.
I am still able to login to my instance.
Skin Rule evaluation order is also same on all servers.
On full.log I found following error while starting MWS server but I am failing to relate it with my problem :

2016-07-20 14:29:12 CEST (com.webmethods.jackrabbit.spi2mws.MwsRepositoryService:ERROR) - Failed to start search manager
javax.jcr.RepositoryException
at com.webmethods.jackrabbit.spi2mws.SearchManager.initializeQueryHandler(SearchManager.java:582)
at com.webmethods.jackrabbit.spi2mws.SearchManager.(SearchManager.java:268)
at com.webmethods.jackrabbit.spi2mws.MwsRepositoryService$1.run(MwsRepositoryService.java:489)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at com.webmethods.jackrabbit.spi2mws.query.lucene.IndexInfos.read(IndexInfos.java:102)
at com.webmethods.jackrabbit.spi2mws.query.lucene.MultiIndex.(MultiIndex.java:249)
at com.webmethods.jackrabbit.spi2mws.query.lucene.SearchIndex.doInit(SearchIndex.java:431)
at com.webmethods.jackrabbit.spi2mws.query.AbstractQueryHandler.init(AbstractQueryHandler.java:45)
at com.webmethods.jackrabbit.spi2mws.SearchManager.initializeQueryHandler(SearchManager.java:580)
… 5 more
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at com.webmethods.jackrabbit.spi2mws.query.lucene.IndexInfos.read(IndexInfos.java:102)
at com.webmethods.jackrabbit.spi2mws.query.lucene.MultiIndex.(MultiIndex.java:249)
at com.webmethods.jackrabbit.spi2mws.query.lucene.SearchIndex.doInit(SearchIndex.java:431)
at com.webmethods.jackrabbit.spi2mws.query.AbstractQueryHandler.init(AbstractQueryHandler.java:45)
at com.webmethods.jackrabbit.spi2mws.SearchManager.initializeQueryHandler(SearchManager.java:580)
at com.webmethods.jackrabbit.spi2mws.SearchManager.(SearchManager.java:268)
at com.webmethods.jackrabbit.spi2mws.MwsRepositoryService$1.run(MwsRepositoryService.java:489)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2016-07-20 14:29:18 CEST (dataAccess:INFO) - XTypeID 0 not found

Please find attached MWS Login page after FIX-installation.

Kind Regards,
Anand

Hi Anands,

sounds like some corrupted files for your MWS instance.

You can try the following:

  • Shutdown MWS
  • Clear the MWS/server/default/temp directory
  • Restart MWS

Can you share a screenshot of the correct (expected) Login Page for comparison?

Please check for the StartpageRules if there are any differences.

Regards,
Holger

Hi Anand,

is this the only instance affected with the Fix installed?

Issue might be related to the following entry in the Fix Readme:


MWS-15541 (MWS_9.7_Fix8)
The My webMethods Server login page does not support basic
CSS customization. When you use the default login page you
cannot easily modify basic CSS properties such as colors and
fonts.

The issue is resolved. As system administrator, you can use a
set of new CSS properties of the Noodle - Twilight skin to
customize the default login page of My webMethods Server 9.5
and later, using the Skin Administration page.

New CSS properties:
align/login-remember-me Defaults the
"Remember me" text of the check box for remembering the login
credentials to the left.
fonts/login-defaults Allows editing the
font style for labels, error messages,remember-me and
placeholder text.
colors/login-input-border Defines the color of
the login page border.
colors/login-text-button Defines the text
color of the login button.
colors/login-button-top Defines
complex gradient colors for the login
button.
colors/login-button-top-hover Defines complex gradient
colors for the login button.
colors/login-button-bottom Defines
complex gradient colors for the login
button.
colors/login-button-bottom-hover Defines complex
gradient colors for the login
button.
fonts/login-errors Specifies changes to error message
text.
fonts/login-button Allows editing the font style of the
login button text.

In addition, the following CSS properties are modified
and/or have new default values:
colors/login
The new value is '#A9A9BB'. 
The old value was '#747d86'.
colors/login-bg
The new value is '#f0f0f0'. 
The old value was '#E2E4D7'.
colors/login-border The new value is '#d9d9d9'. 
The old value was '#c3c8cc'.
fonts/login The new value is 'font-size: 18px'. 
The old value was'line-height: 1; font-weight: normal;'.
Fonts/login-link is now fonts/login-remember-me. 
It defaults to empty.

The following CSS properties have been
removed:
colors/login-title
colors/login-title-bg
fonts/login-title
colors/login-description-bg

For more information about how to modify the look and feel of a
page, and use the Skin Administration page, see "Administering
My webMethods Server".

Regards,
Holger

Hello Herr. Holger,

Please find expected Login Page attached.

start page rules are same.

I also cleared temp folder after shutting down MWS and restarted it. I am still facing the same issue.

I think your latest comment might be the reason but we have installed MWS_9.7_Fix12 and not MWS_9.7_Fix8 (after MWS_9.7_Fix7).

As per your comments I performed following steps but I am failing to see any changes :

  1. Visited page Skin Administration as sysadmin.
  2. Select our skin(that is present on first position on evaluation order)
  3. Changed parent Skin from Noodle to Noodle-twilight
  4. Saved changes.

I think I am not doing it the right way. Can you please suggest me the procedure to resolve my issue ?

Kind Regards,
Anand

Hi Anand,

you will have to change the skin definition to match the new css properties with the values of the old css properties and eventually restore the old default values for the properties that have changed.

Regards,
Holger

Thanks a lot it worked :slight_smile: