Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It was working, and then it stopped, and I'm not entirely sure why.
I'm currently developing two different sites for a client. I have copies up on a development server at their company, both of those are working. Locally, I'm running an XAMPP setup on an XPsp3 Pro machine. One of the two installs work; the other stopped working recently. I've tested it in all browsers on this machine. Here's a link to a screenshot of the errors I receive (happen to have captures it using Chrome for this test, but it seems to error and not load the same way in all browsers):
(see attached screenshot)
If I load the same site on the dev server at the company, it works. The above error happens when I try to access the site in my local XAMPP environment (using a browser on the same machine that XAMPP is running the site, if that matters).
Thinking that perhaps there was something wrong with my XAMPP, I tried the 2nd site to see if it was still working, and it was, both locally and up on the dev server at the company.
I tried blowing away the local directory and copied everything from the company's dev server back down for that site, even backed up the database, dropped my local schema, recreated, and rebuilt, and it still comes up with an error and the fckeditor doesn't load when doing a node/add/page. If it were a data issue, relative to perhaps accidentally adding a page to include/exclude the editor on, I would have expected that to go away when I blasted the database and refreshed it from the dev site that works.
Any thoughts on why this might be happening? Only thing
| Comment | File | Size | Author |
|---|---|---|---|
| xampp_drupal_fckeditor_fail.png | 121.9 KB | notebene |
Comments
Comment #1
notebene commentedWell, as always, seems like I do a lot of work testing before I post one of these, and immediately after posting, I do 'one more test' and it solves the problem.
While this wouldn't seem to me to make a difference (since it works up on the dev server and I pulled a copy from there down locally), I took a copy of the entire fckeditor module out of the site that works locally and laid it over the top of my local site that's failing, and it works again. I suppose it's possible some permissions were changed on that folder or it's subdirectories which were causing it to fail.
At any rate, it appears to be working again.