Forum Replies Created
-
Replies
-
Thanks, Jason
but
– there are lots of posts in that category “nyhetsbrevene” (newsletters):
http://www.dolcevita.no/category/nyhetsbrevene/
– I do not use wpml or any other “language” plugin. Our site is set up in Norwegian, though.
Anyway, it works now and I could rather come back to you if it happens again, ok?
(If it could be helpful to you/ if you think there’s a bug in the theme or something, I could gladly set up an admin login for you to have a look. In case, drop me an email – kjetil@mysite: – that’s dolcevita.no)
Thanks,
KjOK… this is just weird:
I looked up the page once again (as I did 3-4 times before and while I wrote the post above) – and now the post list is in place – and the template looks and works just as it should. The category selector also is there with the appropriate category selected.
The only thing I’ve done after posting was to make a minor change to the page’s content – but I wouldn’t believe that just that should have any influence on the template builder’s functionality…?
Well, now it works. Don’t know what happened.
Cheers,
KjBeautiful!
Thanks, Jason
That works just as I hoped.
…and I’ll just look a bit around for alternative ways to display images – but on the other hand I really like the simple and nice-looking “standard” way of yours. We’ll see :o)Beautiful !
Editing a copy of the content-404.php file (in the child theme folder) worked just as I hoped.
ThanksHi
This works fine for mistyped url’s (like http://www.dolcevita.no/toscanax), but not if somebody performs a search which doesn’t return anything (like http://www.dolcevita.no/?s=toscanax). Is there a way to make the custom (child theme’s) content-404.php appear there too?
Thanks,
Kjetil
(I mainly use Alyeska, but I guess its just the same setup)You are so right. My mistake. Sorry.
I had forgotten to update the theme on nye test site, and with that in place everything works. Of course.
I tried to be quick – thought it would be useful for you too to know – but obviously I was too quick.
Thanks for your explanation
KjetilMaybe I wasn’t clear enough, but I have NOT deleted anything from the mother theme’s core files. I have only changed the span settings (in general.php) for the “double_sidebar_right”.
That should be in accordance with the article you linked to.
The only thing I have removed/ deleted was the css I’ve previously added to my child theme’s custom.css file.The last thing you mention, about the child theme’s function.php file – does it mean I can add the the altered function from general.php there? (The lines from 492 to 550?)
Thanks,
KjWaking up an old topic here… I finally got time and courage to dig into this.
I wanted a layout with a double right sidebar (one wide one narrower) and avoid a problem on smartphones, that the main content (the content field) showed up in half width.
The solution was to remove the custom css for the content area and sidebars (from alyeska-child/custom.css) + to edit the widths of the double right sidebars in alyeska/framework/includes/general (line 539-545) from
'double_sidebar_right' => array(
'name' => 'Double Right Sidebars',
'id' => 'double_sidebar_right',
'columns' => array(
'content' => 'span6',
'left' => 'span3',
'right' => 'span3'
to
'double_sidebar_right' => array(
'name' => 'Double Right Sidebars',
'id' => 'double_sidebar_right',
'columns' => array(
'content' => 'span7',
'left' => 'span3',
'right' => 'span2'
This gave me the narrow outer right (“right”) sidebar and the wider inner right (“left”) sidebar.
IT WORKS!Now, what still puzzles me a bit is that I have to edit a core theme file, which you have warned as several times not to do.
So is there a way to avoid this?
Also, how can I fine-tune the width of the sidebars?
That part I couldn’t figure out from the tutorial you provided above.Thanks,
KjetilThanks for your quick response – but, sorry – I tried inserting those two variations of css into my child-theme/custom.css file, but it didn’t make any difference. The posts and post lists still just fill half the screen width. (There shouldn’t be any other way to do this, right..?)
I don’t believe the new css should interfere with any of my other custom css, since the only other place I’ve touched the .boxed class is in the bottom of the css shown below.
Great if you have other hints :o)
KjetilThis is the main part of my custom css, in case you see something I don’t:
(The part left out is css for images and for some special elements living just on a few special pages.=/* Body’n – bredden på hovedcontainern */
#top, #featured, #main, #bottom, #after-footer {
margin: 0 auto;
width: 1190px;
}
/* Telefonnummer til høyre for headingen fjernet */
#branding .header-text {
display: none;
}
/* Featured-feltet – for smalt nå*/
.element-inner
{
max-width: 1150px;
}
/* (Ytre høyre) høyre sidestolpe */
.double_sidebar_left .left-sidebar, .double_sidebar_right .right-sidebar {
width: 14%;
}/* (Indre høyre) Venstre side stolpe */
.double_sidebar_left .right-sidebar, .double_sidebar_right .left-sidebar {
width: 24%;
}/* Content-feltet */
.double_sidebar_left #content, .double_sidebar_right #content {
width: 56%;
}/* Boksen rundt bildet i featured-feltet: bredden – satt inn width
.standard-slider .slide .media-inner {
background: none repeat scroll 0 0 #FFFFFF;
border: 1px solid #DDDDDD;
border-radius: 4px 4px 4px 4px;
padding: 4px;
width: 1120px;
}
*//* Boksen rundt bildet i featured-feltet: containern rundt boksen – width ned fra 60% til ca 50% */
.tight .grid_fifth_3 {
width: 49.2%;
}
/* skyggefeltet i full-width featured-bildet, lagt inn margin-left, max-width 75-100px, kuttet bottom: 10px; */
.standard-slider .media-full .content {
background: none repeat scroll 0 0 #333333;
color: #FFFFFF;
left: 10px;
margin-left: -10px;
margin-bottom: -10px;
max-width: 100%;
opacity: 0.8;
}/* Metalinja i post-liste – mellom tittel og utdrag – lagt til display: none; */
.single-post .entry-meta, .post_list .entry-meta {
font-size: 11px;
font-style: italic;
display: none;
}/* bredden på nedre del av forsiden, med kolonner el – endret bredde fra 1100px */
#top, #featured, #main, #featured_below, #bottom, #after-footer {
margin: 0 auto;
max-width: 1190px;
}/* Fjernet linje over tabellceller */
.entry-content td, .comment-content td {
border: 0 none;
padding: 6px 10px 6px 0;
}/* Skygge bak enkelte Header-tekster */
span.header-shade {
display: none;
height: 100%;
position: absolute;
width: 100%;
}
.header-shade {
background-image: none;
}
.boxed-layout .header-shade, .post_grid .header-shade, .article-wrap .header-shade, #content .element-slider-standard .header-shade, .element-content .header-shade, #content .element-post_grid_slider .header-shade, .element-post_list_slider .header-shade, #content .element-slogan .header-shade, .element-tweet .header-shade, #comments .comment-body .header-shade, #respond .header-shade, .tab-content .header-shade {
background: none;
}(hm… – thought I could edit a fresh post here…)
…and as you may notice: The “normal” menu lies underneath the Uber-menu on both /blogg and /cucinaCorrection: Also the menu in dolcevita.no/cucina breaks the same way.
Hello again
I have another problem after updating an other part of this site (with its separate wp installation): The menu breaks – as you may see here: dolcevita.no/blogg
Now, this is not a not a normal menu, but a “mega menu” where I use the Ubermenu plugin. It works fine on the other parts of dolcevita.no (the dolcevita.no itself and dolcevita.no/cucina). It worked fine before the upgrade (from framework 2.1.5 to 3.0.2). After the upgrade I have tried to deactivate all other plugins (but Ubermenu) – the menu still doesn’t work. Since I use a child theme with its own custom.css file, I have also tried both using the custom.css file from the main section (dolcevita.no) and switching from the child to the mother theme. No difference.
– Is it likely that the newest version of Alyeska and Ubermenu is somewhat incompatible?
– Any other obvious solution I’ve overlooked?
– Should I rather ask the author of Ubermenu?
Thanks – again
Kjetil
