Home › Forums › Weaver Xtreme Theme › Editor Issues Again
- This topic has 6 replies, 3 voices, and was last updated 7 years, 2 months ago by
Weaver.
-
AuthorPosts
-
April 19, 2015 at 23:59 UTC - Views: 2 #17636
Arro
ParticipantOn a new computer and new website and experiencing Editor issues again, this time all of the Pages > Edit
Well, I cannot show you in full because it keeps saying too many characters too long…..so not sure what to do next if the tiny amount below does not illustrate the problem. I have changed browsers and rebooted, nothing allows me to see a page in the editor.
-
Dashboard
-
Posts
- Posts
- All Posts
- Add New
- Categories
- Tags
-
Weaver Show Posts Options
-
Plugins 0
- Plugins 0
- Installed Plugins
- Add New
- Editor
-
Users
- Users
- All Users
- Add New
- Your Profile
-
Tools
- Tools
- Available Tools
- Import
- Export
-
You can also
embed media from many popular websites including Twitter, YouTube,
Flickr and others by pasting the media URL on its own line into the
content of your post/page. Please refer to the Codex to learn more about embeds.
Parent – You can arrange your pages in
hierarchies. For example, you could have an “About” page that has “Life
Story” and “My Dog” pages under it. There are no limits to how many
levels you can nest pages.Template – Some themes
have custom templates you can use for certain pages that might have
additional features or custom layouts. If so, you’ll see them in this
dropdown menu.Order – Pages are usually ordered
alphabetically, but you can choose your own order by entering a number
(1 for first, etc.) in this field.Edit Page Add New
April 20, 2015 at 00:45 UTC - Views: 1 #21428Weaver
KeymasterThere have been no other reports of issues with the Editor and Weaver.
What if you switch to a different theme – such as twenty fourteen?
Have you disabled all you plugins, one at a time?
Trying to show everything on your editor screen is unlikely to be helpful. By “not being able to see a page in the editor” – could you be more specific exactly what you mean? To you see the page editor window, but no content in it. Do you see something less?
Any chance you’ve specified white characters on a white background?
April 20, 2015 at 14:07 UTC - Views: 1 #21429Arro
ParticipantI disabled plugins one by one (only had a handful activated) and when I deactivated Weaver Xtreme Theme Support the anomaly resolved itself. Apparently, I am good to go. Will try in a moment.
What was happening was that Pages > Edit looked exactly as pasted above from where it says “Skip to main content.” Further down, what looked like the editor window appeared but could not see data that is clearly visible when viewing live online per the link in the OP.
What about the plugin, should I do without it or try it again?
April 20, 2015 at 16:03 UTC - Views: 1 #21430scrambler
ModeratorNot using Xtreme theme support is not really an option, it contains all the shortcodes for xtreme.
But no one else has the issue with it so you probably need to investigate further.
April 20, 2015 at 17:17 UTC - Views: 1 #21431Weaver
Keymaster@Arro –
Almost everyone using Weaver Xtreme has the plugin activated, if for no other reason than it provides all the Per Page and Per Post options on the Page/Post editor pages.
Could you please list which other plugins you were using? What seems
possible is that some other plugin is creating a conflict with the Per
Page options provided by the Weaver Xtreme Support plugin.Does the Post editor also fail (when the plugin is activated)?
April 21, 2015 at 00:44 UTC - Views: 1 #21432Arro
ParticipantThe only ones running were:
- Captcha
- Categories to Tags Converter
- Contact 7
I have activated that Weavr Xtreme Theme Support again as requested. Now it is running normally with the plugin activated. Clearly, as you said, something else was interfering with it. Please let me know if there is anything I can do to help you investigate it.
April 21, 2015 at 17:38 UTC - Views: 1 #21433Weaver
KeymasterI don’t think any of those plugins would affect the editor.
This could just be some kind of transient issue – perhaps associated with some caching somewhere along the line.
But since it started working again, I don’t think there is much left to try to figure out. If it happens again, let us know and we will try some other paths.
-
-
AuthorPosts
- You must be logged in to reply to this topic.