My question is when I change anything in the Example.vue, User.vue or any of my Vue components and refresh my browser it doesn't get the updates at all, the old values still remain. Even if I delete the entire code in any of my components it's still there. I clear my browser cache, restart the computer, run dev, npm run watch, ran dump-autoload, Php artisan clear cache. I am using laravel 5.8. I am running or of ideas. Any ideas.
Thanks
Do you have supervisor running on your pc? If you do, run
supervisorctl restart all
read more here
and here
Related
I am trying to make changes to the Spark Laravel BillingPortal.vue page. After making a change I know the the app.js is being compiled but I see no change in the billing page.
I have cleared the cache in Laravel and the browser and still not luck.
I can completely delete all code on the page and still nothing happens. It is still the same in the browser.
Please tell me how to change this file.
The BillingPortal.vue file compiles into Spark's /public/js/app.js file, so in order to see any updates you'll need to rebuild Spark's JavaScript separately from your application's assets.
cd vendor/laravel/spark-stripe (or vendor/laravel/spark-paddle if you're using Spark Paddle)
npm install
npm run dev
That being said, it's not recommended that you make changes to Composer packages because the changes will be overwritten when the package is updated. Instead choose one of the options mentioned in these answers
So, I installed everything as directed in the documentation, both the node-template and front-end template. Then, I went on to run ./target/release/node-template --dev --tmp in the node-template directory, which worked fine and was able to produce blocks. After opening a new terminal and moving to the front-end template, I used the command yarn start. This didn't produce any error and I was redirected to https://localhost:8000/front-end-template. The site took too much time to load and I was not able to see the Polkadot UI. Looks like the front end could not be integrated with the node-template.
Any help would be much appreciated.
In the front-end template directory while the node-template is running,
run yarn install and after everything works well then yarn start
OR, remove the front-end template and clone a new one if you didn't make significant changes to old one.
OR, stop the node-template and run this command ./target/release/node-template purge-chain then start the front-end.
I used do these and get this problem fixed, quickly!
I have a fresh installation of laravel 5.4.
I have successfully created a new component and displayed it correctly.
I use npm run watch and my .vue files get compiled correctly.
But now, any changes I make to the .vue files do not get updated.
I purposely made errors to them to see if they compiled but they failed, so I conclude that the watch command successfuly sees changes made to them, on the other hand, nothing updates in the browser (only blade files update).
Any ideas what this could come from ?
PS: I tried php artisan cache:clear but no success.
Silly, the name of the component had a dash in it:
Vue.component('cardtest-component', require('./components/CardTestComponent.vue'));
It was just a typo.
I have a composer packege which i want to modify, it is part of Laravel framework, but i want to modify it big time. For that i need the xdebug to be able to run via the composer.
To be precise it runs on composer post update hook and there is a error in it.. i can not get it to work, but cant debug it. Anyone has any idea how i can do it?
I tried to do it via command line to test it, but i don`t get any meaningful answers. And i dont know how to run composer command in browser where i have a xdebug command active.
You can very easily get Xdebug remote debugging on the command line as well. No need for a browser. You simply do:
export XDEBUG_CONFIG="idekey=sangoku"
and then run the composer script. As long as you have xdebug.remote_enable set to 1 in php.ini, this will initiate a debugging request to an open IDE. Depending on your IDE, you might need to do something special though to allow this connection to come in.
I created an SQL installation script for my extension and it ran just fine. I was developing the extension with the caches turned off. When I turn the caches on, the installation script doesn't get run, and I can't work out why.
I've tried clearing all of the Magento caches through the admin panel, flushing the cache storage, manually removing the contents of the magento/var/cache folder, clearing the APC cache, clearing the redis backend from the command line and restarting the PHP process, and nothing has worked. The only way I've managed to get the installation script to run is by turning the caches off.
Does anyone know why this would be happening? I'm using Magento v1.4.0.0 RC1.
An installation-script should run only once, and only if you tell Magento to do so by updating the version of your modules config.xml. This config gets cached, so clear all your caches and reload a page... It should run the installation script.
You can always reset the way Magento is used to run installscripts, by resetting the version for your module in the database (in the core_resource table of your magento database).
Update scripts are run by Mage_Core_Model_App::_initModules() method, but only when the cache is empty or disabled.
So make sure that you do not access the module configuration in any way before the Mage::run() call in index.php.