CSS Error Message And Uploading Image

[JJ]

Forum URL: (private)
I'm working at a test site, so did not give the address.

I'm trying to create a new Theme. I keep getting this message:

"We're sorry. There was a problem loading the editor due to errors in your CSS file. You must manually fix your CSS here before you can proceed."

(I also get that error message on my home site.)

I click on the Here but that just takes me to the CSS area. No clue to what it is referring too.

I want to create a new theme from scratch. But I cannot seem to use the Proboards image Host to install a background.

Now, I can import an existing pbt file that has that same background image, but it has a lot of junk on it that I don't want for a new theme. I'm trying to start fresh. 

Any ideas?

Thanks for your help.

[Craig]

Hi JJ

Unfortunately, i can't see the css file, so will label this for the attention of the staff who will be able to take a look and see what the problem may be. Please check back a little later today for a reply from one of the reds

[Scott]

JJ, it's been about 13 hours since your initial post. Is this still occurring? Also what is the name of the theme you are having an issue with?

[JJ]

Hi, @socals. I hadn't tried today, so I just did. I chose several to try. This time I just started clicking the themes at random, and that message popped up all of them immediately.

[Scott]

JJ, I was unable to reproduce any error messages. Can you please walk me through the steps you are taking. Thanks.

[JJ]

Ok, Scott . Nothing fancy today. I just would go to Admin, Themes, Advanced Styles and CSS, and this happens.

 

[Brian]

Both myself and Scott performed these same steps in the same browser but were unfortunately unable to reproduce this issue.

Have you updated or changed anything recently? I recall you having this issue before in a prior thread:
support.proboards.com/thread/650872/problems-css-editor

It's worth noting that all of our tests are performed on the latest version of Windows 10 so there shouldn't be any issues in that regard.

[JJ]

I remember that incident, Brian . I wonder if it's Firefox? Wait, I have Windows 10 Pro, what were you using?

ETA: No, I have not changed anything.

ETA: I went to check, and I have had some updates in the security system.

[Brian]

We're using Windows 10 Pro as well.

If you think it's Firefox you're welcome to try to duplicate it in a different browser purely for deductive purposes.

[JJ]

Will do, Alexander .

ETA: Ok, that's the problem,  no error message in IE. Any suggestions other than use IE? I don't like Chrome, but IE is a dinosaur.

ETA: Are you using FF Quantum? I had a lot of problems that in FF and had to get an older version.

[Brian]

Yes. We always use the latest version of all of our supported browsers.

[JJ]

Ok, thanks, Brian. Guess I'll bite the bullet. I have the version I'm using saved, not that it's doing me any good anyway. Guess I'll update. *shudder* I'll let you know if that's a fix so you can use the info to help others.

[Kami]

JJ, keep in mind that this is frequently true of other websites and software companies too, not just PB so they can stay abreast of each browser's updates (including but not limited to security and performance issues).

If you're having issues with a browser on a machine, it's generally best to a) see if that machine is capable of handling that application (sometimes older machines are simply incompatable with newer software), and b) if it's meant to be compatible check with the software company -- in this case, Mozilla / Firefox -- to see what can be done about it. (:

[JJ]

Thank you, Kami . My computer is only a few years old, 1T drive with 16 gig of ram, it can handle just about anything.

Scott and Brian , Updated FF and I'm back in business. Just used the Proboards host to add a background over at my test site and it worked like a charm!

Thanks for all the feedback. JJ

[Kami]

Oh if that's the case then, when you encounter errors like that it's always good to contact the application developer -- there may be some issues with the latest build that they hadn't encountered in testing and feedback would always be welcome as opposed to just switching to an older version (: