Question about a possible bug in the interface

[laura]

I just upgraded to version 2.0 on one of my test sites and I first noticed that there was a customized 1px blue border that I had defined between my preheader and header was missing, so I went in to check the settings. The CSS statement was fine. I activated the customizer and was able to redefine a border, but it was a default black border.

The bigger problem was after I published the site with the border back in, I wanted to return to the WordPress dashboard. I pressed the “X” in the upper left corner of the customizer  and got an error 404 from Hostgator. I can click the <– arrow to get back to the interface, but I cannot get back to the WordPress dashboard.

I’m finding the new interface a little traumatizing right now because I’m in the middle of a project and I’m not yet ready for the learning curve. Is it ok to stay with the regular Weaver interface until I’m ready to take the new one on? Will the regular interface still be available in future versions?

If you need a link to the site, I was working on this test site: http://clientswebdesigns.com/blog/

This is the first site that I upgraded. I don’t know yet of other problems with my other test sites.

 Thank you,

Laura

   

[laura]

In the traditional settings, I went back in and added a line in the header area to add a blue border around the header, even though I only wanted it at the bottom of the preheader, but this is good for now.

I just went into the customizer and figured out how to navigate back to the Legacy interface, however should I still have gotten that 404 error by clicking on the “X” at the upper left corner of the customizer?
 
General Options & Admin –> Legacy Weaver Xtreme Admin –> Weaver Xtreme Admin
 

[scrambler]

If now is not a good time to take risks with the Customizer, you can keep using the Legacy Admin Interface. It will always be there.

As for the problem you had, none are normal.

• Can you elaborate on where/how the border was defined?, and did it disappear from the public site, or was just missing in the customizer settings?
• The 404 is definiteky not right. @weaver will have to see if he can reproduce that

[laura]

Hi Scrambler,

The border was defined originally in the Main Option –> Font & Custom (CSS Rules box)

The style that was working is still there. It’s the style line referring to the border bottom of a prewrapper img that comes before the main banner in the head section:

#inject_prewrapper img {
width: 100% !important;
max-width: 908px !important;
margin: auto !important;
border-bottom: 1px solid #006fbf !important;

After the upgrade to 2.0, that style no longer worked, but I was able to override it by going to:

Main –> Header

In the Header Area background, I added the following:   {border: 1px solid #006fbf !important;} (but I only really needed the border at the bottom of the preheader, but this will do for now.  I had to change the rounded corners from all to just the bottom of the header.

That 404 is also happening on another installation. I just “X” out of the customizer rather than navigating out.

[scrambler]

If you say your original CSS is there but does not produce any result, we need to look at it as it may cause more issues.

The CSS you pasted in above is missing a closing curly bracket after the rule. If this is really the case, it may be your issue, If not, can you remove your work around and post a link to the site not showing that border, so we can figure out what is wrong?

#inject_prewrapper img {
width: 100% !important;
max-width: 908px !important;
margin: auto !important;
border-bottom: 1px solid #006fbf !important;}

[laura]

Scrambler,

The closing curly bracket is there, but it was posted at the bottom and I missed it when I copied it over to you, sorry.
I removed the temporary fix so you could see how the site looked after the upgrade to version 2.0

#inject_prewrapper img {
width: 100% !important;
max-width: 908px !important;
margin: auto !important;
border-bottom: 1px solid #006fbf !important;
}

http://clientswebdesigns.com/blog/

[scrambler]

This comes from your rule on the pre-wrapper that has a negative bottom-margin of 7px

#inject_prewrapper {…….margin-bottom:-7px;}

It would need to be -6px for the border to show. Right now it is covered by the piece below.

Not sure why the value would have to change, but the space you were trying to remove comes from the default font size combined with the image link.

For a better fix, remove the margin-bottom:-7px;  from that rule,  and instead put in

font-size:0px;

That will get rid of the space exactly

[laura]

Thank you so much, Scrambler!

The first fix worked just fine, but the second is better?

Please alert Bruce about the 404 errors.

Thanks again,

Laura 

[scrambler]

Yes the second is better as it removes the cause for the space.

Using a negative margin is a band aid that will fail if the cause changes slightly (as it did).

So get rid of the negative margin rule, an use the zero font size rule instead

[Weaver]

I have no idea about the 404.

I cannot reproduce any issues with exiting from the Customizre using the X in the top left. That is how I always do it myself.

There is one possible thing that can happen. If your login times out, or if something about the Dashboard menu changes behind the scenes, when you exit the Customizer, it no longer knows where to exit to.

There are not that many ways to open the customizer. You can enter from the Dashboard via Appearance : Customizer, from the Themes menu when the theme thumbs area shown, and from the Legacy Weaver Theme Options interface. I think the Admin menu at the top may allow this at times, too, although I can’t find that option at the moment.
 
Whenever you enter the Customizer via one of these methods, a parameter is actually passed to the Customizer where it was opened from. For example, if you have the Dashboard Widgets menu open, and then use the Appearance : Customizer to enter the customizer, you should see something like //example.com/wp-admin/customize.php?return=%2Fwp-admin%2Fwidgets.php on your browser address bar. Note the ?return=%2Fwp-admin%2Fwidgets.php part – that is telling Customizer who opened it, and where to go back to if you click the X exit button.

So, to get a 404 when you click the X means the return= is no longer valid for whatever reason – maybe your login expired. I’ve had that happen, and have had to fix the address bar to /wp-admin to get back to the admin page, for example. But I’ve never seen a 404, and don’t know what might have happened. I suspect it won’t happen after you logout/login, and start from a fresh top-level /wp-admin page.

[laura]

Hi Bruce,

I upgraded a bunch of sites yesterday, but only tested the Customizer on three, and this happens on all three.

I even “X’ out right after I got in as a test, so there wasn’t any time for my log in to time out.

When I activated the Customizer from the Legacy Weaver Themes Options interface, my browser address bar looked like this:

http://clientswebdesigns.com/blog12/wp-admin/customize.php?return=%2Fblog12%2Fwp-admin%2Fthemes.php%3Fpage%3DWeaverX

After I “X” out, my browser address bar looked like this and I get the 404:

http://clientswebdesigns.com/blog12/wp-admin/themes.php?page=WeaverX

So I can only exit the Customizer when navigating the menus of the Customizer itself. I cannot exit out normally by hitting the “X” which takes me back to the Legacy Interface.

[Gillian]

Whether I go in to the Customiser from the Appearance menu or from the Weaver Xtreme legacy interface, and then ‘X’ out I am successfully returned to the page I started from.

Perhaps you have some plugin interaction going on?

[Gillian]

Actually, having just read this post on another thread

http://forum.weavertheme.com/discussion/comment/62014/#Comment_62014

it appears as if both posters may be having issues related to them using the Customiser on a subdomain.

Edit – I did actually mean subdirectory (and would you believe I checked cPanel to get the correct name and it called both subdomains and subdirectories as subdomains!)

[laura]

Hi Gillian,

You might be right about that. I just tested the Customizer on a production site that is not on a subdomain, and I was able to “X” out and it took me back to the Weaver Xtreme 2.0 Options screen, so running it on a subdomain may be an issue. But it seems to function ok, I just can’t exit out by pressing “X”. 

[scrambler]

@weaver will have to review this, I had similar issues on a WordPress installation in a sub folder during beta. 

May be Wordpress installations in subdomains have a similar set of issues

[Maureen]

I just updated to Weaver X 2.0 and now cannot access the Customizer on my subdomain. Worked fine in the earlier Weaver X version.  Getting an “Internal Server Error” message.

[Author]

Posts