What's New in WOW - Category: Bug Fix http://blogs-it.cgaux.org/WOW_news.php?tempskin=_atom b2evolution 2025-04-29T19:14:29Z Text and Heading Centering Bug Has Been Eliminated admin http://blogs-it.cgaux.org/WOW_news.php/2012/09/08/text-and-heading-centering-bug-goes-splat 2012-09-08T04:49:45Z 2012-12-18T17:09:29Z WOW users who have had difficulty in centering text or headings with the "center" icon will be pleased to know that a bug was found in the custom CSS styles that are part of WOW.  That bug is now splattered on the windshield of progress. Centering works now on all tags, both in the Cute Editor, and on the rendered web page.  You may have to flush your browser's cache to drive out the old CSS.

]]> The Member ID and Password text boxes disappear from the Member Zone Login window. Kevin Redden http://blogs-it.cgaux.org/WOW_news.php/2012/05/04/the-member-id-and-password-text-boxes-disappear-from-the-member-zone-login-window 2012-05-04T02:06:40Z 2012-05-05T03:30:35Z A problem unique to the Cute editor used in WOW can result in the Member ID and Password fields disappearing in the Login window, so that members cannot login to a WOW web page. This occurs in rare cases when the Import WOW-I button resulted in some bad html code being inserted into the top of a WOW II page. This also results in a ¼” deep white bar showing to both sides at the very top of the page.

  1. The fix is to remove the bad lines of html code by editing the page(s) involved:
  2. Login by gaining access to your site by using the generic WOW login at http://wow.uscgaux.info.
  3. Go to the Configuration Dashboard, and edit the page in question. This will bring up the page in WOW’s Cute editor.
  4. Switch to HTML view in the editor instead of Normal view (select HTML on the lower left of the editor window).
  5. At the top of the page in HTML view, look for and delete all code between successive sets of <style type=>……</style> tags. Do this until you get to a tag <.....> that is not <style>. These problem lines at the top of the page will look something like the following examples:

    <style type="text/css" isprelink="true">@import url(http://wow.uscgaux.info/cuteeditor_files/Style/SyntaxHighlighter.css);</style>
    <style type="text/css">@import url(../content_cute.css);</style>
    <style type="text/css">@import url(php.css);</style>
  6. Note that each of the problem code lines always begins with “<style type=”, and end with “</style>“. There could be anywhere from one to more than thirty of these lines that need to be stripped.
  7. Go to the bottom of the page, look for and delete any lines that also say the same as #4 above, starting at the last line, and working backwards to the first non-style tag.
  8. Save the page.
  9. View the unit page, and confirm that the white bar is gone, and the member login boxes appear again.

 

]]> Your Auxiliary Email Address is "uscg.mil"? You May Not Be Able to Configure WOW admin http://blogs-it.cgaux.org/WOW_news.php/2012/04/04/your-auxiliary-email-address-is-uscg-mil-you-cannot-configure-wow 2012-04-04T19:53:07Z 2012-04-14T13:09:41Z If the Member Zone password you set up was validated using a uscg.mil email address (that is, your primary email address listed in AuxDirectory/AuxOfficer is your.own.name@uscg.mil, then you may not be able to configure either WOW or the Public Education Database. Currently, 0.37% of Auxiliary members have uscg.mil email addresses.

The reason is that AuxOfficer categorized you as an active duty member when you applied for the password, even though you are a member, starting fall of 2011.

If you fall into this category, simply revisit the AuxDirectory/AuxOfficer sign-in page, and from there request a new password (it can be the same one) using "Obtain/Change Password". Or, just click this link.

]]> Safari Browser (Macintosh or PC): Don't Use for WOW Editing! admin http://blogs-it.cgaux.org/WOW_news.php/2012/03/17/safari-browser-macintosh-or-pc-don-t-use-for-wow-editing 2012-03-17T09:33:13Z 2012-03-17T09:33:13Z There is a problem with the Safari browser on both Macs and PCs: images inserted into your WOW page cannot be edited after insertion in the WOW announcement editor.  This is a problem specific to Safari, and does not occur with other browsers.

If you are a Safari user (usually only Macintosh users), please download and use Firefox as your default browser for working with your WOW site.  www.firefox.com

The guts of the editor are licensed froma 3rd party, and it may not be possible to fix this Safari limitation in the near future.

]]> Licensee Error (1) Host Not Match! admin http://blogs-it.cgaux.org/WOW_news.php/2012/01/26/licensee-error-1-host-not-match 2012-01-26T18:25:57Z 2012-01-26T18:30:19Z If you get the error "Licensee Error (1) Host Not Match!<some URL>" when trying to enter data into the Announcement editor (Cute Editor), it is because you accessed the page via a corrupted URL -- usually from a bookmark -- that combines portion of a correct URL with additional incorrect pieces.  The only correct URL for accessing your site is its "canonical" address (see the User's Guide).  For example, if your unit number is 115-03-07, then your site's canonical URL is "a1150307.wow.uscgaux.info".  That is the address you should bookmark, and that is the address that you should share.

If this happens, throw away any bookmarks that you have saved to access your site, close your browser (all copies), and revisit the site with the canonical address.  If you persist in getting the problem, take a screen shot, save the image file, and use the "Feedback/Support" button in the Dashboard to ask where to email the screen shot.

]]> Bug Fix: Future Announcements admin http://blogs-it.cgaux.org/WOW_news.php/2012/01/01/bug-fix-future-announcements 2012-01-01T11:25:28Z 2012-01-01T11:27:02Z The expectation is that announcements with a future start date will not appear until that date. This was not occurring, and future-dated announcements were showing up now. This has been fixed. Note that if you have any content that has mysteriously "disappeared", check to see if it mistakenly had a future start date.

]]>