Digital experiences for all disciplines
New Landing › How can we help? › Themeforest Theme Support › Dante › Issues after updating dante to newest version
New Landing › How can we help? › Themeforest Theme Support › Dante › Issues after updating dante to newest version
- This topic has 16 replies, 2 voices, and was last updated 9 years by Swift Ideas – Ed.
-
Posted in: Dante
-
July 25, 2015 at 5:16 am #197625
hi guys,
Issue #1. Entire website is no longer full width. All content is not full width even though options are set for full width…. Screen shot is attached.
Issue #2. Every page has title showing even though option is set to off. Screen shot attached.
Issue #3 portfolio showcase widget has gaps on both sides. Screen shot attached.
Attachments:
You must be logged in to view attached files.July 25, 2015 at 10:36 am #197636Hey,
Did you check the sticky? Tried to login to your site but looks like there is a file missing – not sure if you are replacing the parent theme?
Can’t remember – are you using a child theme?
– Ed
July 25, 2015 at 10:44 am #197637Hi Ed,
I came across your other post about the width issue and tried the page builder resave but that didn’t work. So i am in the process of loading the old version of dante right now. When i tired to rewrite the old dante over the new one I still had some of the issue. So now i have deleted the dante folder all together and reloading the old version. Old version is now loaded.
And yes I do have a child theme but always thought the child theme was specifically used so something like this wouldn’t happen???
thanks
July 25, 2015 at 11:01 am #197638Ed,
Now that old version is loaded back I still have page builder problem where it says section is undefined. So I seem to not be able to fix any of the row or out of place content anymore. never had this problem with older version of dante. All problems seem to be happening on homepage.
Thanks
Attachments:
You must be logged in to view attached files.July 25, 2015 at 11:08 am #197640Yes – that is what child themes are for, but with major theme upgrades where we potentially change the structure of the theme, edits to core files are needed. It’s best if you take the new file and copy your new changes to that file. The changes are mainly in the header files, page.php, single.php, single-portfolio.php etc.
– Ed
July 25, 2015 at 11:15 am #197641Ed,
So even though I am back to old version of dante and still have the undefined error, will what you just advised still work?
Also I am not positive what parts of the child theme are edited? So how can I know for sure which files need to be replaced in the child theme? I am pretty lost to what files are causing the problem. And I wouldn’t want to rewrite custom files I need. Any advice?
Thanks
July 25, 2015 at 11:21 am #197643The undefined error will be because of the page builder being changed to the new version (with adjusted code). It should still work on the frontend, although if not you likely have revisions on the page you can revert to?
– Ed
July 25, 2015 at 11:31 am #197645Ed,
Thank god the revisions fixed the undefined error. ๐
So let me get this straight i should update to version 3.0 now? Then take files from new dante 3.0 and add them to child theme?
Thanks
July 25, 2015 at 11:35 am #197646What we’d advised to do is compare any files in your child theme with the new parent theme files, you could use a tool such as http://www.diffnow.com/
Basically you want to add your changes into the new version. We’ve improved the structure so that the page heading output is a function, rather than in each file for example.
– Ed
July 25, 2015 at 11:44 am #197652Ed,
Ok I apologize if I’m not catching on fast. Might be because its 630 am here and i haven’t slept yet. ๐ lol
So Im just trying to make sure I get this right. So any files I find that are different I Add new dante 3.0 files to dante child theme or old child theme files into new dante 3.0?
And if i find a file that’s different do I replace the whole file or just the part that’s different?
Thanks
July 25, 2015 at 11:56 am #197653No problem, I know the feeling well!
So what you want to do is check one by one each file in your child theme. Ideally you want to replace that file with the file from the parent theme, and then re-add your changes. It will be easier to work it that way.
– Ed
July 25, 2015 at 12:07 pm #197654ed,
Ok…..
#1. Find different file.
#2 Add new version of different file from parent theme into Child theme.
#3 save
Right?
Thanks
July 25, 2015 at 1:12 pm #197660Yes – but only your changes, not every difference.
– Ed
July 28, 2015 at 5:36 am #198376Ed,
I haven’t upgraded again to version 3.0 yet but I have noticed some other people are having the same issue I had. After reviewing my Child theme I really only have two php files in there a functions.php and single.php. And none of them seem to be related to the issues I had.
The functions file only changed pagination from title to prev and next.
The single file only has this in it:
// OVERWRITE PAGE BUILDER ASSETS
// function spb_regsiter_assets() {
// require_once( get_stylesheet_directory_uri() . ‘/default.php’ );
// }
// if (is_admin()) {
// add_action(‘admin_init’, ‘spb_regsiter_assets’, 2);
// }
// if (!is_admin()) {
// add_action(‘wp’, ‘spb_regsiter_assets’, 2);
// }
//mod content
function hatom_mod_post_content ($content) {
if ( in_the_loop() && !is_page() ) {
$content = ‘<span class=”entry-content”>’.$content.'</span>’;
}
return $content;
}
add_filter( ‘the_content’, ‘hatom_mod_post_content’);//add hatom data
function add_mod_hatom_data($content) {
$t = get_the_modified_time(‘F jS, Y’);
$author = get_the_author();
$title = get_the_title();
if ( is_single() || is_page()) {
$content .= ‘<div class=”hatom-extra”><span class=”entry-title”>’.$title.'</span> was last modified: <span class=”updated”> ‘.$t.'</span> by <span class=”author vcard”><span class=”fn”>’.$author.'</span></span></div>’;
}
return $content;
}
add_filter(‘the_content’, ‘add_mod_hatom_data’);So I wanted to verify this before changing things for no reason.
Thanks
July 28, 2015 at 1:38 pm #198550Hi @camind
The issue will be the single.php file override – there will likely be the page heading output still in there if it’s override from an old version of the theme.
– Ed
-
Posted in: Dante
You must be logged in and have valid license to reply to this topic.