PeterPan Posted April 26, 2022 Posted April 26, 2022 I just updated to the latest bleeding edge version and now on my dashboard there is nothing displayed. just an empty site. Any ideas? I also have his Database problem? but when i click apply, there isn´t a solution, but an error.
PeterPan Posted April 26, 2022 Author Posted April 26, 2022 (edited) Update: Almost on every page nothing is displayed Edit: rolling back to stable version fixes the issue. But it is maybe a bug in latest bleeding edge version. I did the update from bleeding edge version circa a month ago Edited April 26, 2022 by PeterPan
wakabayashi Posted April 26, 2022 Posted April 26, 2022 https://github.com/thirtybees/coreupdater/issues/22 the DB issue is known. But it's not the reason for the other problem... I am not on the newest bleeding edge, so I dunno. But sounds surprising to me.
wakabayashi Posted April 26, 2022 Posted April 26, 2022 I tried an update with my clean installation. The dashboard issue is not there. I guess you should check the browser console. 1
datakick Posted April 27, 2022 Posted April 27, 2022 @PeterPan These are two issues. 1) Dashboard not visible after update -- I can't confirm. I just updated my test and production env to bleeding edge, and have no problem. You will need to look into your server error logs to see what is there. Also, what php version are you using? 2) Regarding DB schema problem with auto-increment column migration -- as @wakabayashi, this is known issue, and will be fixed in upcoming version of the core updater
toplakd Posted April 27, 2022 Posted April 27, 2022 @wakabayashi You could try to delete your overrides one by one if you have any for admin area. To see which one is causing the problem. I'm updating my live site now as I had to make some small updates to my carrier overrides which generated error when updating Coreupdater didn't add that column, neither displayed option in database schema due to missing line in my override 🙂 I do all my updates on backup copy of shop first, to eliminate all the possible issues (mostly no issues) and to check if my overrides work 🙂
datakick Posted April 27, 2022 Posted April 27, 2022 25 minutes ago, toplakd said: Coreupdater didn't add that column, neither displayed option in database schema due to missing line in my override 🙂 I do all my updates on backup copy of shop first, to eliminate all the possible issues (mostly no issues) and to check if my overrides work 🙂 Did you redefine the object model definition in your override? public static $definition = [...] If so, what were your reasons to do it?
toplakd Posted April 27, 2022 Posted April 27, 2022 (edited) Yes, $definition was redefined in my override and bottom line was missing. That missing line was the cause of my error when updating, and preventing database schema to add this column 🙂 'display_name' => ['type' => self::TYPE_STRING, 'lang' => true, 'validate' => 'isCarrierName', 'required' => true, 'size' => 64], Edited April 27, 2022 by toplakd
toplakd Posted April 27, 2022 Posted April 27, 2022 My reason to redefine was due to enhance the carrier options based on weight and cart price combined. 1
datakick Posted April 27, 2022 Posted April 27, 2022 6 minutes ago, toplakd said: Yes, $definition was redefined in my override and bottom line was missing. That missing line was the cause of my error when updating, and preventing database schema to add this column 🙂 'display_name' => ['type' => self::TYPE_STRING, 'lang' => true, 'validate' => 'isCarrierName', 'required' => true, 'size' => 64], We really need some better way to extend object model definition. Currently there are few methods do to it, but none of them is good enough, or work in all use cases. I have seen full override (the one you have used) -- since this is not an extension of parent definition, it is very brittle. Another way to do this is to 'adjust' object model definition in constructor. That method works in some cases only, though. 2
toplakd Posted April 27, 2022 Posted April 27, 2022 This are the changes I'm using for 2 years now and working without issues for my use. https://github.com/thirtybees/thirtybees/pull/1170
wakabayashi Posted April 27, 2022 Posted April 27, 2022 52 minutes ago, datakick said: We really need some better way to extend object model definition. Currently there are few methods do to it, but none of them is good enough, or work in all use cases. I couldn't agree more. 😎 You see I am adding a lot of PR these days. But this is out of my reach. A very very good understanding of TB and PHP is needed. 1
PeterPan Posted June 20, 2022 Author Posted June 20, 2022 (edited) On 4/27/2022 at 8:16 AM, datakick said: @PeterPan These are two issues. 1) Dashboard not visible after update -- I can't confirm. I just updated my test and production env to bleeding edge, and have no problem. You will need to look into your server error logs to see what is there. Also, what php version are you using? 2) Regarding DB schema problem with auto-increment column migration -- as @wakabayashi, this is known issue, and will be fixed in upcoming version of the core updater so i tried today again to update to latest bleeding edge. PHP Version is 7.4; MySQL is 5.7 opening he browser console shows this or any other ideas, where the problem could be located? this is what it looks like Edited June 20, 2022 by PeterPan
datakick Posted June 20, 2022 Posted June 20, 2022 @PeterPan Most likely you have override for template admin/themes/default/template/controllers/dashboard/helpers/view/view.tpl. This template is responsible for displaying the dashboard page Look recursively in your /override/ directory for file named view.tpl
PeterPan Posted June 20, 2022 Author Posted June 20, 2022 I can´t remember changed this file. This is in the file {* * 2007-2016 PrestaShop * * NOTICE OF LICENSE * * This source file is subject to the Academic Free License (AFL 3.0) * that is bundled with this package in the file LICENSE.txt. * It is also available through the world-wide-web at this URL: * http://opensource.org/licenses/afl-3.0.php * If you did not receive a copy of the license and are unable to * obtain it through the world-wide-web, please send an email * to [email protected] so we can send you a copy immediately. * * DISCLAIMER * * Do not edit or add to this file if you wish to upgrade PrestaShop to newer * versions in the future. If you wish to customize PrestaShop for your * needs please refer to http://www.prestashop.com for more information. * * @author PrestaShop SA <[email protected]> * @copyright 2007-2016 PrestaShop SA * @license http://opensource.org/licenses/afl-3.0.php Academic Free License (AFL 3.0) * International Registered Trademark & Property of PrestaShop SA *} <script> var dashboard_ajax_url = '{$link->getAdminLink('AdminDashboard')}'; var adminstats_ajax_url = '{$link->getAdminLink('AdminStats')}'; var no_results_translation = '{l s='No result' js=1}'; var read_more = '{l s='Read more' js=1}'; </script> <div id="dashboard"> <div class="row"> <div class="col-lg-12"> {if $warning} <div class="alert alert-warning">{$warning}</div> {/if} <div id="calendar" class="panel"> <form action="{$action|escape}" method="post" id="calendar_form" name="calendar_form" class="form-inline"> <div class="btn-group"> <button type="button" name="submitDateDay" class="btn btn-default submitDateDay{if isset($preselect_date_range) && $preselect_date_range == 'day'} active{/if}"> {l s='Day'} </button> <button type="button" name="submitDateMonth" class="btn btn-default submitDateMonth{if (!isset($preselect_date_range) || !$preselect_date_range) || (isset($preselect_date_range) && $preselect_date_range == 'month')} active{/if}"> {l s='Month'} </button> <button type="button" name="submitDateYear" class="btn btn-default submitDateYear{if isset($preselect_date_range) && $preselect_date_range == 'year'} active{/if}"> {l s='Year'} </button> <button type="button" name="submitDateDayPrev" class="btn btn-default submitDateDayPrev{if isset($preselect_date_range) && $preselect_date_range == 'prev-day'} active{/if}"> {l s='Day'}-1 </button> <button type="button" name="submitDateMonthPrev" class="btn btn-default submitDateMonthPrev{if isset($preselect_date_range) && $preselect_date_range == 'prev-month'} active{/if}"> {l s='Month'}-1 </button> <button type="button" name="submitDateYearPrev" class="btn btn-default submitDateYearPrev{if isset($preselect_date_range) && $preselect_date_range == 'prev-year'} active{/if}"> {l s='Year'}-1 </button> </div> <input type="hidden" name="datepickerFrom" id="datepickerFrom" value="{$date_from|escape}" class="form-control"> <input type="hidden" name="datepickerTo" id="datepickerTo" value="{$date_to|escape}" class="form-control"> <input type="hidden" name="preselectDateRange" id="preselectDateRange" value="{if isset($preselect_date_range)}{$preselect_date_range|escape}{/if}" class="form-control"> <div class="form-group pull-right"> <button id="datepickerExpand" class="btn btn-default" type="button"> <i class="icon-calendar-empty"></i> <span class="hidden-xs"> {l s='From'} <strong class="text-info" id="datepicker-from-info">{$date_from|escape}</strong> {l s='To'} <strong class="text-info" id="datepicker-to-info">{$date_to|escape}</strong> <strong class="text-info" id="datepicker-diff-info"></strong> </span> <i class="icon-caret-down"></i> </button> </div> {$calendar} </form> </div> </div> </div> <div class="row"> <div class="col-md-4 col-lg-3" id="hookDashboardZoneOne"> {$hookDashboardZoneOne} </div> <div class="col-md-8 col-lg-7" id="hookDashboardZoneTwo"> {$hookDashboardZoneTwo} </div> <div class="col-md-12 col-lg-2"> <section class="dash_news panel"> <h3><i class="icon-rss"></i> {l s='thirty bees News'}</h3> <div class="dash_news_content"></div> <div class="text-center"><h4><a href="https://thirtybees.com/blog/" onclick="return !window.open(this.href, '_blank');">{l s='Find more news'}</a></h4></div> </section> <section class="dash_links panel"> <h3><i class="icon-link"></i> {l s="Useful links"}</h3> <dl> <dt><a href="https://docs.thirtybees.com/" class="_blank">{l s="Official Documentation"}</a></dt> <dd>{l s="User, Developer and Designer Guides"}</dd> </dl> <dl> <dt><a href="https://forum.thirtybees.com/?utm_source=back-office&utm_medium=dashboard&utm_campaign=back-office-{$lang_iso|upper}&utm_content=download" class="_blank">{l s="thirty bees Forum"}</a></dt> <dd>{l s="Connect with the thirty bees community"}</dd> </dl> <dl> <dt><a href="https://store.thirtybees.com?utm_source=back-office&utm_medium=dashboard&utm_campaign=back-office-{$lang_iso|upper}&utm_content=download" class="_blank">{l s="thirty bees apps"}</a></dt> <dd>{l s="Enhance your store with templates & modules"}</dd> </dl> <dl> <dt><a href="https://github.com/thirtybees/thirtybees/issues" class="_blank">{l s="GitHub issues page"}</a></dt> <dd>{l s="Report issues in the Bug Tracker"}</dd> </dl> </section> </div> </div> </div> 1 hour ago, datakick said: @PeterPan Most likely you have override for template admin/themes/default/template/controllers/dashboard/helpers/view/view.tpl. This template is responsible for displaying the dashboard page Look recursively in your /override/ directory for file named view.tpl
PeterPan Posted June 20, 2022 Author Posted June 20, 2022 the thing is, the statistic at the dashboard didn´t work since a long time. Maybe there is a connecton to this
datakick Posted June 20, 2022 Posted June 20, 2022 Again, investigate overrides / modules. Try to disable overrides and check if dashboard works -- if it works, investigate which override is a culprit Try to disable non-tb modules and check that dashboard works -- if it works, then enable non-tb modules again, and disable individual modules to figure out which one is the culprit This is not a bug in core, it's very specific to your installation. Nobody can help you much without access to your back office and/or error logs 1
PeterPan Posted June 20, 2022 Author Posted June 20, 2022 so overrides I do not have. And I disabled all non tb-moduls (wich are only a few) but didn´t change anything...
PeterPan Posted June 20, 2022 Author Posted June 20, 2022 I am not good in technical details. I used prestashop 1.6 and moved to thirtybees in the end of 2019, more or less "out of the box" I did not change anything manually
PeterPan Posted June 21, 2022 Author Posted June 21, 2022 Quote Fixed. Problem was caused by overrides from modules that were no longer installed on my system: Especially overrides from packageweight module caused a lot of problems, because it redefined object model definition. Core updater used this (invalid) object model definition and migrated database table to wrong / unexpected state. Since I no longer use this module, the overrides needed to be deleted manually, and the database table to be regenerated. Thanks for the help
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now