duena_studio

Hi @slado777,
Can you please give link on your site? There can be couple reasons of this problem:
1) In 2.0 was changed Twitter Bootstrap version and old bootstrap css maybe was cached in your browser, to check it – try to open site in another browser, where you didn’t opened it before.
2) If you use some caching plugin on your site – they may cache old version of your pages with incompatible HTML markup, if you use such plugins – try delete old cache – such option or similar must be in each of this plugins.
3) If you use child theme and rewrite there some theme templates – replace in them bootstrap layout classes with new – for example ‘span8’ -> ‘col-md-8’, ‘span4’ -> ‘col-md-4’ etc. In 2.0 there are no backward compatibility for child themes based on old versions – it was our mistake, we’ll fix it with future updates.
If you give link on your site – I’ll could find reason in your case

Almost certainly this solve the problem – every theme have own set of defined image sizes and all images are cropped to this sizes only once after uploading, so every time when you switching theme you should to regenerate thumbnails

Hi,
You need to rewrite in your Child theme file comments.php, then find there next code:

$args =  array(
    'comment_notes_after' => '<p class="form-allowed-tags">' . sprintf( __( 'You may use these <abbr title="HyperText Markup Language">HTML</abbr> tags and attributes: %s' ), ' <pre>' . allowed_tags() . '</pre>' ) . '</p>'
);

and replace it with:

$args =  array(
    'comment_notes_after' => ''
);

Hi,
Can you please give link on your site.

This background inherited from Notifications plugin CSS file.
To fix this you need to create child theme for Duena (or use some plugin for adding custom CSS code) and add there next code:

.post_meta.default {
    background: none;
    border-top: 1px solid #EBEAE7;
}

Hi
You may use Excerpt field on writing posts screen to set manual summary as you wish. This summary will shown on home page.

@nipponshin – yes, all look right now

Maybe I should disable wp super cache…

seems like it makes sense to try