Topic Closed

Hi

The improvements in 3.0 look fine and valuable. Small point if not already seen, the long box - Page Options, Layout etc. which arises from selecting a page under the Main Menu list is not visible in Chrome.

8 years ago#3918

jogai
264 Posts

I cant reproduce the problem with version 3.0b2

8 years ago#3924

Hi

Definitely happening, using an up to date, stable version, as below:

Google Chrome 19.0.1084.52 (Official Build 138391) m
OS Windows
WebKit 536.5 (@118056)
JavaScript V8 3.9.24.28
Flash 11,2,202,235
User Agent Mozilla/5.0 (Windows NT 5.1) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.52 Safari/536.5
 
I should have taken a screen shot, have since ripped those files out. Did manage to throw some back and reproduce similar as in the image below, with just the top border visible:
 
 
On the first occasion, nothing else was abnormal, just the box not there at all. Could be related to my other post you replied to, the theme CSS. When possible, I will be trying again from scratch with a different (safer) framework and post an image if the issue comes back.
Edited: 8 years ago#3927

Charles S
448 Posts
13.7K Downloads
2 Themes
8 Plugins

I'm either not understanding the problem or don't have it in 3.0b2

 

here's a screen shot of me in my main menu with the floating admin menu

 

 

What am I missing?

8 years ago#3931

What am I missing?

Most likely nothing, the probability is that my theme experiments are the issue and the problem will not exist for most.

From two different responsive themes, one simple, one substantial, the same sort of issue. One exactly as your screen shot but without the box, the other more wrecked as above. Just tried with a more normal css file and can't reproduce the problem either.

Not going to hijack this thread/section but will keep playing with responsive possibilities, would be useful.

8 years ago#3937

Charles S
448 Posts
13.7K Downloads
2 Themes
8 Plugins

Make sure that you user something like #user_content in your theme to differentiate your styling from gpEasy's. Because gpEasy is designed to work via the front end styling can really conflict with a theme's. Therefore, it's best whenever possible to add a specific class and/or ID to your theme and style with those to ensure your styling is applied only to non CMS stuff.

8 years ago#3938

That sounds like a good approach. Have been making a little progress, ignore the missing box in so far as was theme related. The dark grey backgrounds from the admin block also eliminated for now with:

 

#admin_menu li div a.label {
  background-color: inherit;
  }
 
A few other bits and pieces but all problems created by the theme/framework, not gpEasy. 
8 years ago#3940

Charles S
448 Posts
13.7K Downloads
2 Themes
8 Plugins

Yes, it's been a difficult thing to get gpEasy CSS to play nice with theme CSS due to the front end & inline WYSIWYG editing — it was lots of fun when first getting that going lol. There's only so much Josh can do to avoid conflicts the rests needs to be done by theme developers to ensure they are only styling for content & extra content areas.

 

Best of luck!

8 years ago#3941

Josh S.
2K Posts
285K Downloads
16 Themes
18 Plugins

it's been a difficult thing to get gpEasy CSS to play nice with theme CSS

This is definitely one of the biggest challenges of our approach. The first part of the admin.css file that attempts to address common issues, but there are certainly more.

Instead of

#admin_menu li div a.label {
  background-color: inherit;
  }
 
would this solve the conflict you're seeing (added to the top of admin.css)
body #gp_admin_html *{
    background:none;
}
 
Edit: scratch that idea. Setting background:none conflicts with too much admin css.
Edited: 8 years ago#3959

Interesting thought though Josh and I will come back to these issues at some stage. May well change the framework anyway, try a few others, or combine & custom build. Get what is required running off gpEasy, then meld the two, trying to sort both in tandem isn't good.

For anyone reading in general terms, worth considering use of border-box on an element by element basis, not globally. In terms of navigation change for smaller devices, easiest approach is to switch to a select box, rather than interfere with core navigation. Few issues with that, although I've spent a while trying to create true collapsible navigation direct from the gpEasy main menu, not quite right yet:)

8 years ago#3967

Topic Closed

 

News

elFinder 2.1.50 in Upcoming Release
12/28/2019

A new release for Typesetter is in the works with a lot of improvements including the ... Read More

Typesetter 5.1
8/12/2017

Typesetter 5.1 is now available for download. 5.1 includes bug fixes, UI/UX improvements, ... Read More

More News

HH-Support

Company located in T├│rshavn, Faroe Islands. * Webpage Design * Consultant & Provider of a wide range of programs for visually impaired and dyslextics.

Find out more about our Provider Spotlight

Log In

  Register