Home › Forums › Weaver Xtreme Theme › Preparing a replacement page fully mirrored …
- This topic has 56 replies, 4 voices, and was last updated 6 years, 7 months ago by
Dave.
-
AuthorPosts
-
March 28, 2017 at 16:17 UTC - Views: 82 #47814
Dave
ParticipantUpdate: Restored Xtreme, since my freezing issues appear not to be theme related. Also; with Xtreme, the sub-menu “bump-out” referenced above doesn’t happen. Nice!
Still working, and learning. Sorry for the repeated questions. 🙁
Best,
David
March 28, 2017 at 23:52 UTC - Views: 77 #47836scrambler
ModeratorFor starter, you seem to have some HTML syntax errors.
Your page has more than one <body> tag, and that is not allowed. Only the theme add one body tag (opens at the beginning and closes at the bottom.
If you added content with body tags, you need to fix that. No content you add should include any <body> or </body> !
Running your site through HTML validation, also reports open nor closed <div> tags, and that is also a cause for errors. Check ALL HTML you put in and make sure that for every opening <div> there is a closing one </div> and vice versa
March 29, 2017 at 00:25 UTC - Views: 71 #47839Dave
ParticipantAhhhh
Scrambler-
i did add some HTML body tags to some widget text. I’ll need to look into this. What strikes me odd is Weaver II Pro seems uneffected by this. It’s been running flawlessly for years. 🙁
OK so absolutely no <body> tags anywhere and check for open
tags. Got itBest,
David
March 29, 2017 at 00:49 UTC - Views: 69 #47840scrambler
ModeratorI have no idea if this is the cause of the issue, but HTML errors give unpredictable results as each browser attempt to auto correct in a different way, and the smallest change in content can create a different result in that auto correct attempt.
You may have a site that appear to work, then change one things and it falls apart.
To test for HTML errors, run each piece of HTML you inserted through an online validator
https://validator.w3.org/#validate_by_input
But to be honest, HTML errors usually cause the layout to break, not the site to hang that is more usually related to a bad script or something, so we will see.
Finally, when testing to disable plugins, make sure that you clear ALL caches (especially cache plugins), or you may not see the benefit of deactivating them
March 29, 2017 at 00:54 UTC - Views: 70 #47841Dave
ParticipantHi Scrambler. I found the following in one of my widgets
<body bgcolor=”#F5EADD”>
<p align=”center”><font face=”Times New Roman”>
<font color=”#000000″ size=”6″>Raptor Bay</font><font color=”#000000″><br>
<font size=”4″>Project Information</font></font></font></p>
</body>If I disable the text widget and make it inactive, the tags are still there so I’ll need to delete it completely right?
Best,
David
March 29, 2017 at 01:05 UTC - Views: 60 #47842Dave
ParticipantScrambler-
Just for bells and whistles I eliminated the body tags and replaced it with this …
March 29, 2017 at 01:33 UTC - Views: 65 #47843Dave
ParticipantScrambler-
I removed all body tags I could find. On the bottom left sidebar I had a rather large text file with numerous hyperlinks via several HTML body tags. I completely deleted that also.
I ran Xtreme through several rapid page changes which no doubt would have caused it to lockup. So far, no lockups and running smooth and quick.
Thank you sooooo much for looking into the code and providing me with this information. I’ll find an alternate way of getting that information there without body tags.
I’ll keep checking and running the site. So far, so good (fingers crossed).
Thanks again my friend.
Best
David
March 29, 2017 at 02:29 UTC - Views: 60 #47846scrambler
ModeratorYou can keep the same HTML, just remove the open and close body tag.
If the body tag had styling, move it onto the actual elements.For example where you had
xx
You can just use
yy
And actually, using old HTML tags for styling should be replaced by CSS, so the correct HTML would be
zz
If you are not too HTML savy, you can use a plugin like Black Studio Tiny MCE widgets (https://wordpress.org/plugins/black-studio-tinymce-widget/) which have the Editor tools inside the widgets, or you can use the content editor of a test page to type and format your text, then switch the content editor to text mode, and copy paste the HTML from there into your widgetMarch 29, 2017 at 02:30 UTC - Views: 60 #47847Dave
ParticipantThanks Scramber-
This was an awesome find on your end. I’ve been pounding the Xtreme beta site and not a singe lockup. You mentioned something about the bottom of the page. Well, when the page goes into responsive mode, the left side bar goes to the bottom and at the very bottom of that is where I had a slew of HTML body tags. It was text to various departments with hyperlinks to each.
I have used the test page method you described, then switch to text and copy the code into a text widget. In fact, I do it that way to link the widget pictures seen.
The culprit text widget I created HTML using MS FrontPage (bet you remember that product), then I’d cut and paste the HTML code a text widget. A practice I will absolutely discontinue.
Thsnks again for all your help. You obviously know your stuff. 👍🏼
Best,
David
March 29, 2017 at 02:35 UTC - Views: 40 #47848scrambler
Moderator
@weaver, I cant seem to post HTML examples in a post any more, it gives me the error 403, even if the HTML is in a preformatted tag…March 29, 2017 at 02:38 UTC - Views: 33 #47850Dave
ParticipantThanks for the tip and link. I will download that plugin tomorrow and recreate the links I removed.
Thanks again, I’ll keep everyone posted.
Best,
David
March 29, 2017 at 04:12 UTC - Views: 31 #47851Weaver
KeymasterIt might be helpful to edit the wp-config.php file in the site root and set the WP_DEBUG to true to see if there is some plugin or other part causing a fatal PHP error.
March 29, 2017 at 09:37 UTC - Views: 28 #47859Dave
ParticipantAll-
I’ve been running the site hard and not a single lockup. Scrambler, thanks much for that find … it was driving my blood pressure up.
If I may ask, is there a way to make the hamburger menu icon and menu within larger?
Best,
David
March 29, 2017 at 10:35 UTC - Views: 31 #47862scrambler
ModeratorAdd the rules below in Main Options > Fonts & Custom > Custom CSS Rule box
.menu-toggle-button {font-size:150% !important;}.is-mobile-menu a {font-size:120%;}March 29, 2017 at 13:08 UTC - Views: 34 #47865Dave
ParticipantScrambler/Weaver-
I had all Weaver plugins disabled before, so I enabled them to implement Scrambler’s custom CSS code for the increase menu size. However, when I activated them all, the site froze up again. It froze while I was activating them but not until I reached the WP Edit plugin. Right then in the control panel it froze. When I went back to the mobile device it started doing the same thing all over again. I have now deactivated all Weaver plugins and mobile site seems to be running smooth again.
I’ll activate each Weaver plug in (one at a time) and leave the WP Edit plugin for last to see what happens.
@Scrambler: I inserted the CSS code you sent and it increased the font size (I went a tad larger), but the actual hamburger menu starts out larger for a split second, then reverts to the smaller size. 🙁
@Weaver: PHP stuff is a bit deep for my simpleton mind. You may have to go easy on me Mr. Weaver, as my skill set is nowhere near to teh power coders you have here. 🙂I’ll keep you posted.
Best,
David
March 29, 2017 at 13:45 UTC - Views: 15 #47866Dave
ParticipantScrambler-
Before I start activating plugins I added the plugin you suggested: https://wordpress.org/plugins/black-studio-tinymce-widget and it works beautifully. I restored the information on the bottom of the left column and it looks great, with no [body] html coding. 🙂
OK, off to start activating plugins one-by-one ..
Best,
David
-
AuthorPosts
- You must be logged in to reply to this topic.