Forum Activity for @soaringeagle

sb causes doubled styling due to forced containers

Using Jamroom

the old sb allowed you to put a tab container then widgets within it in any widget space
the new sb forces you to put widgets in containers so the container and widget are both styled creating a double styling (one item wuthin another both getting the item style)

to replicate turn on sb run integrity check to disable old sb components clear cache

the only thing i can think of to fix this would be to rename the container item to something like container-item to allows it to be styled separately, or not at all
but where would that be found
updated by @soaringeagle: 12/22/16 11:55:59AM

site builder buttons do not show

Using Jamroom

the site builder buttons do not show up on ningja, slate, or the default skin, on 1 site only
on other site and i believe dev site it works correctly

to replicate, turn on new sb, run integrity check to disable old sb, only 2 menu items show clear cache the rest of the menu items show but you cannot access sitebuilder

as a test i went to pages that do not exist, it ga ve the option to create the page, i did, but could not edit it because of no sb buttons

updated by @soaringeagle: 12/22/16 11:55:59AM

page created in sb (old version) only shows up when logged in

Using Jamroom

ok ill make a thread about each issue separately then

page created in sb (old version) only shows up when logged in

Using Jamroom

ok i created a page in sb old version since new version does not work
i went to a diferent browser logged out got a 404 not found
i logged in, the page worked
i cleared and disabled sever caching i cleared the data/cache folder manually and the page continues to say not found unless logged in

i expected the same results as every other page i created in sb it to be visible whether logged in or out


actual, it only shows when logged in

additional info
maybe unrelated maybe not
when checking the code for the widget to see if there might be anything in the code causing it, it replaced my containing div and classes with a p and, additionally applied the classes i had applied to the div to every p
it took 3 tries to correct that as it kept replacing them when id save


final notes because i am still having issues with sb new version i may require more help updating to it
the issues with sb new version are
the page edit buttons do not show up
every widget gets double styling because its forced to be within a containing div that is styled if theres a way to rename that containing item to widgetcontainer or something that should solve that but the buttons still do npt show up so i cannot use the sbo additionally, there are 2 empty menu items that are there .. you see the styling around where the buttons should be but nothing inside them
they are on either side of the home button

All the issues i am having with sb core are the same issues i have had with it since early beta
at one point you had tried to get it to work and told me to just remove 1 class name but that only marginally helped it was still a mess

page created in sb (old version) only shows up when logged in

Using Jamroom

in the error console i get "permission denied to access property "document""
and
"permission denied to access property "tostring""
updated by @soaringeagle: 03/21/16 04:28:12PM

page created in sb (old version) only shows up when logged in

Using Jamroom

i see theres a new sb update
i'll give it 1 more shot

page created in sb (old version) only shows up when logged in

Using Jamroom

that's how i always do it
but as i said i cant get sb to work at all
ive been begging for help to get it to work for months now
i have tried so many times

page created in sb (old version) only shows up when logged in

Using Jamroom

this page https://www.dreadlockssite.com/set-up-your-own-shop
gives you a 404 when logged out, but shows up when logged in
additionally i still cannot use the new sb or ningja skins cause the sb buttons don't show up and the forced use of a container causes a double styling issue
example
the styling of the area with the h1 tag or the activity feed show up within a styling of item:1st of type
the h1 tag area should not be forced to be within an item 1st of type
but is
the activity feeds placed inside an item that doesn't need to be there
we should be able to add the tabbed or vertical continers wo a widget space and not be forced to use them
like the old version allowed
updated by @soaringeagle: 12/22/16 11:55:59AM

old test domain in notification emails after server restore

Design and Skin Customization

i don't
i built the site on a test domain once it was ready, i simply changed the domain

weirdest thing is it worked just fine till recently after the db screwup
and now I'm again getting the sonso commented on @ thing again too

still cant use sitebuilder buttns missing etc

Using Jamroom

i dont mean a container class i mean a extra containing div
the container the widgets go on and the widgets themselves have the same class i think item that makes it redundant and doubles up the styling like i saifd yoir forced to put a widdget inside a container ...the old 1 thered be no extra containing itemno doubled up styling
and it does the same thing on the default skin, and on the unmodified ningja skin