Upgrading Wagtail from 2.9.3 to 2.11 breaks wagtail admin icons - wagtail

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...

Related

PimCore X Not Loading

I've been following the guide found here, https://unixcop.com/how-to-install-pimcore-on-ubuntu-20-04/, to install the PimCore X version from scratch on a fresh server.
However, after going through all of the steps and firing up the initial home page, I get the profiler complaining about a number of 404 errors for resources that it cannot find within the /_wdt/ folder, with the profiler never loading.
The admin section of PimCore cannot be loaded either, it comes up with a big 404 error, so I'm guessing that the router isn't working properly. Looking into the log files for both PimCore and Apache, there isn't anything useful to be found.
I've tried to install PimCore several times, each with the same result.
Any help would be gratefully received.
It turns out that the .htaccess file within the /public/ folder wasn't being installed with the fresh install. The .htaccess file contents can be found here, https://pimcore.com/docs/pimcore/current/Development_Documentation/Installation_and_Upgrade/System_Setup_and_Hosting/Apache_Configuration.html
Best way to install Pimcore are using docker.
You can read it on github page https://github.com/pimcore/skeleton
All that you need is install docker.
You can do it from this link https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04

Wagtail version in admin interface does not update after upgrade

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.

Hot reload stopped working after adjusting environment for work requirements

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.

Using create-react-app's npm startwith AWS Cloud9

I am attempting to use create-react-app in AWS Cloud9. While I have no problems creating the app, when I try to run npm start I just get this screen. When I clicked on "Why am I seeing this?" I was taken to this page, which led me to turn on HTTPS. While HTTPS was enabled, it did not fix the issue. create-react-app's Github page suggested that CHOKIDAR_USEPOLLING=true is required for virtual machines, but that also did not fix the issue: it now creates a blank page, as shown here. Finally, thinking that perhaps the issue was due to some accidental change, I deleted the directory and made a fresh one, but the issue persisted.
Any insight on how this can be resolved would be appreciated.
I had a similar issue. For me I was just going about it the wrong way and I can preview my application by going to Preview at the top of the IDE and then Preview Running Application.

Drupal error "CKEditor is already installed" when trying to install

I installed CKEditor, but for some reason, when I opened the configuration, Drupal says: "CKEditor not installed."
I deleted the folder from sites\modules\ckeditor, then tried to install a different version. On trying to install, it still said "CKEditor is already installed", even though I'd deleted it (and checked it was no longer in the list of modules).
I guess there might be some trouble with the database.
How do I solve this?
Im idiot. Cause I opened by mistake a different FTP, user and was looking at different folder all/sites/modules.....in this folder I deleted everything, but of course the web I was working on had different module folder :-(. So it kept telling me CKEDITOR was installed why I couldn see it... I ll shoot myself soon. Sorry.

Resources