I just add this
active = fields.Boolean(string="Active", default="True") then upgrade the module, but that happening,is there any answer why is that happen?
Related
Updated geckofx45 to 60 as in browser keep showing message like "this browser is not supported anymore please update your browser" and once I updated my solution references, I get 12 errors :(
I tried to look here if I did not find similar issue but for me it doesn't helped.
I tried also update framework from 4.5 to 4.6 then to 4.7.2 even more errors like 102 !
So I'm not sure why this happens, but I know I need the latest gecko browser it order to load website correctly and get rid of message "update your browser"
https://ibb.co/PD1tY5g
I was using prestashop on hosting with no problem.
Now I started my home web server and I'm trying to get it working.
I tried many different prestashop versions and reinstalled them x times..
All the time problem is that, I can Access front panel, but not the backend panel..
All the time it shows Http 500 ERROR : Server can't Handle this request.
Now I enabled debugging and it shows me error:
Fatal error: Declaration of AdminLoginControllerCore::viewAccess() must be compatible with AdminControllerCore::viewAccess($disable = false) in C:\xampp\htdocs\Shop\controllers\admin\AdminLoginController.php on line 27
And Line
class AdminLoginControllerCore extends AdminController{
I can't understand why this is happening, becouse I haven't edited and changed any file or folder.
It happens because you have to implement a method in a child class with all parameters of a parent class method. So in your parent class viewAccess has a parameter $disable=false and you need to have it in your child viewAccess() declaration. Just put that parameter in the declaration public function viewAccess($disable=false) and you even need not use it inside. And why it was not showing on the hosting but show in a local machine it is sooner in due to different PHP versions on the servers. Because in different versions it has different error levels.
The way to fix this is simple:
go to ROOT/controllers\admin\AdminLoginController.php
al line 153 you’ll have to change
public function viewAccess() to public function viewAccess($disable = false).
I had that issue with a fresh installation of PS 1.7 yesterday but did'nt come out of it. Today, apparently the same one with PS 1.6.18, thought I was expecting it would'nt, but it seems that PS can't stand PHP 7.2.4, no matter which PS version it is (of course I should have guessed that a previous version would'nt make it better than a recent one ...). Some PHP warnings might have turned into fatal errors now. The fact is, when I went into controllers/admin/adminLoginController on line 153 and typed public function viewAccess($disable = false) instead of public function viewAccess() the blank screen went away and my back-office was there (with some remaining warnings ...). Those files would'nt have to be overwritten to allow upgrade, but anyway 1.6.18 is the last upgrade of 1.6 series... Hope it can help.
last time I had issues on loading plugins with aurelia-cli and the component i18next (Error: "Plugin.load is not a function").
The (temporary?) solution was to set the aurelia.json configuration "build.loader.stub" to false (Solution).
Now I have the question what "stub" exactly means and if it's really ok to change this global setting permanently to get that one component working?
What is the impact having that configuration "false"?
In the official aurelia documentation I only found a very rough explanation that I don't understand (Aurelia Doc).
Update 1
According to the aurelia-cli repository discussion with EisenbergEffect:
vegarringdal commented on 28 Jul 2016
#EisenbergEffect
You can close this issue if having the "stub" set to false wont break anything..
EisenbergEffect commented on 28 Jul 2016
Nope. There's no problem with that. Setting stub to true just doesn't embed the full text loader. If you need to dynamically require text, you will just want to set that to false. It's absolutely supported both ways. Our HUB actually sets stub to false.
When I upgrade to Accord Framework 3.2.0 and run software I get 2 'obsolete' errors:
Warning 1 'HiddenMarkovClassifier'<'MultivariateNormalDistribution'>'' is obsolete: 'Please use HiddenMarkovClassifier'<'TDistribution, TObservation'>' instead.'
Warning 14 'BaumWelchLearning'<'MultivariateNormalDistribution'>' is obsolete: 'Please use BaumWelchLearning'<'TDistribution, TObservation'>' instead.'
There is no apparent API for the BaumWelchLearning'<'TDistribution, TObservation'>'. When I go to the new API for HiddenMarkovClassifier'<'TDistribution'>' and the relatively minor changes reflected on that documentation it does not fix the 2 issues above.
Any suggestions?
The was answered in updated documentation for Accord Framework in Google Groups Support : https://groups.google.com/forum/#!topic/accord-net/CdB4vsUNr_Y
Is it possible to disable the new the explain functionality in Rails 3.2 globally via configuration? I'm using activerecord-sqlserver-adapter 3.2.1 and there appear to be some bugs with the explain (show plan) portion of the gem.
To cite from http://weblog.rubyonrails.org/2011/12/6/what-s-new-in-edge-rails-explain/
New applications get
config.active_record.auto_explain_threshold_in_seconds = 0.5
in config/environments/development.rb. Active Record monitors queries and if they take more than that threshold their query plan will be logged using warn.
[...]
By default the threshold is nil in the test and production environments, which means the feature is disabled.
so just set
config.active_record.auto_explain_threshold_in_seconds = nil
You can disable auto-explain by setting config.active_record.auto_explain_threshold_in_seconds = nil in your config/environments/development.rb
You should note that config.auto_explain_threshold_in_seconds has been completely removed in Rails 4.0 & 4.1. In 4.1 it will throw a full error.
See https://github.com/rails/rails/pull/9400/files
If you upgrade, comment that line out.