I recently incrementally upgraded my Wagtail installation from 2.15.2 to 2.16.2, but the Wagtail version in the admin interface is still stuck in the old version. What can I do to fix this?
As #LB Ben Jonston suggested, in the end the problem was even though the Docker image was built correctly, the image did not deploy correctly.
Since I'm not very familiar with Azure, I only checked that the pipeline ran correctly, image was built and pushed. But I missed checking that the actual CD task deployed the image successfully, which it didn't.
Related
I have integrated the electron app with the auto-updater and published the electron app as well. I am able to receive the newer version pop-up and able to upgrade my electron app but when I relaunch the installed electron app the app shows the previous version information and asks to install the newer version again. Any suggestions?
I bumped across your question because I was having the same issue. I was using auto-updater with Quasar framework. Maybe this could help someone else.
Since nsis was configured by default to do the oneClick installations (with predefined rules), it was always installing my application somewhere in users/AppData folders, which I didn't even notice.
The thing I was running over and over again (after successfully auto-updating application) was actually installing the previous version all over again.
To circumvent this issue, I changed nsis configuration to allow users to select their own installation path.
nsis: {
oneClick: false,
allowToChangeInstallationDirectory: true
}
After this, app shortcut was appearing on desktop, which was always running the latest version.
I started a new developer role a few days ago and made some environmental changes to adapt for work. Since then, my hot reload/fast refresh has just stopped working entirely. Changes don't show up even if I refresh the page manually. Only shows changes when I stop the dev server and restart it with 'npm run dev'. The triangle indicator at the bottom right should be active, showing active reload of the window (this no longer shows up consistently either, and if it does the page gets reloaded, but alas the proposed changes aren't visible)
Context:
It has this effect on all NextJS and react applications of mine. Even running a basic project template off the NextJS examples page shows no hot reload working.
I researched this issue and it seems wrong imports (e.g. importing components using lowercase or files in the pages directory being capitalized) can cause this, but I combed through the code and can't spot any issues (of course, I could be missing it but my codebase is over 300 files).
Service workers in the background can cause issues, but I cleared my browser of all of them to be sure and it still doesn't fix it.
I installed ngrok for tunneling for work purposes and docker-compose to handle the work dev. environment.
Made sure I'm using the latest Next version. Even deleted node_modules and ran npm install. Deleted .next and the out folder and still no luck.
Anybody have any ideas or clues to what I should try next? Is it related to the stuff I installed for work? Something related to VS code or WSL2? Seems so puzzling it kind of just happened overnight. Thanks for any insight or advice!
System information
OS: Windows (WSL2 virtualization for VS code)
Browser: Chrome
Version of Next.js: 10.0.3
Version of Node.js: 14.8.0
Deployment: npm run dev for development work; amplify publish for AWS hosting
The problem is with WSL2. I use WSL2 inside VS Code; which is a big performance upgrade in the Linux environment. The problem is WSL2 is actually in a 'virtualization' and thus cannot send information from VS Code AND the browser (localhost:3000) at the same time.
It's a big issue they are working on and there is no fix yet for it. That's why fast refresh doesn't work because localhost is not receiving the changes being made. Either proxy through or revert back to WSL1 https://github.com/microsoft/WSL/issues/4769
Solution provide by OP on question section
Add a .env file or a .env.local file to your root and put this line on it:
WATCHPACK_POLLING=true
Now, restart your server.
Thanks I encounter the same issue with WSL2. I just switch to windows terminal and it works.
If you run Poweshell as administrator and run
wsl.exe -l -v
This will give you th eversion of wsl your distros run on.
I am personally using Ubuntu, and this is the output
Ubuntu Running 2
docker-desktop Stopped 2
docker-desktop-data Stopped 2
To switch to wsl 1,
Run
wsl.exe --set-version Ubuntu 1
and if you wanna switch back,
run,
wsl.exe --set-version Ubuntu 2.
This worked for me.
In my react projects, I just add in my .env file at the root project folder the values
FAST_REFRESH=false
CHOKIDAR_USEPOLLING=true
and it works! enjoy!
The problem is with WSL2. I use WSL2 inside VS Code. But React JS and Next JS projects don't auto-reload. So, add a .env or .env.local (recommended) file to your root and put these lines on it:
WATCHPACK_POLLING=true
CHOKIDAR_USEPOLLING=true
Now, restart your server.
I've checked everything...
After upgrading interface looks like this:
Totally broken, but the only thing that is breaking everything is icons...
Neither CMD or DevTools doesn't seem to show any missing files...
I have already ran all of the commands makemigrations, migrate and collectstatic --clear.
Running manage.py check didn't show up any errors.
Checked(disabled/enabled) all of the apps, didn't work.
Checked urls.py on any misconfiguration with staticfiles, still nothing.
Compared my base.py, dev.py files with fresh install of 2.11, didn't see nothing that can cause overriding CSS or JS(I'm using Django Debug Toolbar, tryed disabling it, didn't work, same as everything). Help. Please.
And also on a fresh install there was no "SKIP TO MAIN CONTENT" button on top. I don’t know what that has to do with anything
Wagtail 2.11
Django 3.0.11
Using Pipenv for virtual environment
Damn! Of course, after posting a question, I found an answer. When running collectstatic I've noticed that there was too many Found another file with the destination path... messages, but did not take this into account. Then I realized that somehow in my core app staticfiles folder were duplicates of Wagtail's core static files, so I installed Wagtail 2.11 for the millionth time, ran the server and nothing changed... Fortunately, I've guessed(thanks to #gasman) to clear cache and reload the window and IT WORKED!
Conslusion: Check for duplicated static files, mine were from the old version of Wagtail, but Wagtail is on latest, which caused this issue...
I made some fixes for my App and wanted to try it out today on my iPhone and now I can't install it on the device anymore. I'm getting the error "Unable to Download App" on the phone.
I haven't changed anything on my Apple Developer Account and yesterday everything was working fine. Is this a known bug and does anybody know how to fix this? My iPhone is of course registered and I also did the "iOS Certificate Wizard" and built it again but it didn't work either.
Edit: So I was able to install the app after doing the complete Certificate Wizard again with also overwriting everything (which I had not done before), but now I made another build and I can't install it again! Do I really have to do the Wizard thing every time I send a build now?
Are you trying to install a distribution build on top of a development build, or vice-versa? If so, uninstall the existing app first.
I'm trying to start using hipster. I've completed the installation and tried to recreate the same bookstore app like in the demo video.
Everything went well (installation, app creation, app startup, DB schema creation) but when I access the application in the browser, I only the text "This is your footer". I don't have the header and the body like in the demo. There is no error in the console. I assume something is wrong with AngularJS but I don't know what.
I'm on Mac OS 10.10
JDK 1.8._45
eclipse Luna (I've successfully imported the generated hipster project as a Maven project)
If you have any suggestion on where to investigate. Thanks.
Ok, the root cause was that the bower components were not properly installed.
To resolve the issue, I've done:
sudo xcodebuild -license (without agreeing with the license, it was
preventing bower to complete)
sudo bower install --allow-root (to download all the components)
Had the same problem in Google Chrome. Fixed by clearing cache and cookie.
Maybe, it`s help you too.
in my case i used a postgresql database. I changed the user password in both application-dev.xml and application-prod.xml and also on the database.
alter user myuser password 'mypassword' ;
then restarted the app with command mvn sprint-boot:run
then it worked