JohnDar

I have applied the patch and can now see the (allegedly) customised CSS. However, there is still no way to compare it with the standard version to see what might have changed. There is also no way to revert it.
I could go in and hack about in Designer mode, but if everyone is faced with doing that, this change might be counter productive in terms of support volumes?
I think my suggestion in the reply above might be the best solution for both yourselves and customers?

Thank you.
Going forward, maybe the best solution would be to have all CSS showing but read-only, with the ability to revert if differences are found?

Not recently, but I have now no way of comparing the two versions to see what's going on and no way of reverting if something is amiss. That's a bit of a setback and more of a 'downdate' than an update.
I have always used the access to the standard CSS files to determine what code to modify (along with the syntax etc), before adding it to my custom CSS. I can't do that now, which is going to make any future additions to the custom CSS far more difficult for me to accomplish.
 

Same problem here, following upgrade to 4.7.0.
With "Advanced theme editing" enabled, I can only see core-front-custom-custom.css. None of the other css files are showing. I have also run the support tool and cleared the cache and the issue remains
I made a note of css files I need to revert, after updating but now I'm hamstrung and can't do the reverts.

Looking closer, it may have been the quicksearch template at fault, but this wasn't flagged up as requiring attention. 😞
 

I have just applied the latest update. It flagged two CSS files that were incompatible. Both were reverted before updating. However, once the update was applied, photo attachment thumbnails were missing. This indicated that there were other CSS files which needed attention and a check with the default theme confirmed this,(I couldn't see anything amiss in the templates).
However, there was no way of determining where the issues might be. The only CSS file available for me to edit was custom.css. No others were showing up as modified. I had absolutely no way of checking for other modified CSS, with a view to reverting them.
My only way out of this was to copy the default theme and then laboriously go through every tab, modifying the colours to match my customised theme. I then had to edit the resources and add in all my custom mods. I then had to add in the custom CSS from the broken theme.
This worked and I'm back up and running, but it's two hours of my life that I won't get back. Previously this type of fix would have taken me about two minutes.
Needless to say, I'm deeply unhappy with the removal of the edit feature and concerned about how some edits don't seem to have been picked up, leaving me with no way out other than a ground-up rebuild.

Thank you.
Going forward, maybe the best solution would be to have all CSS showing but read-only, with the ability to revert if differences are found?

Not recently, but I have now no way of comparing the two versions to see what's going on and no way of reverting if something is amiss. That's a bit of a setback and more of a 'downdate' than an update.
I have always used the access to the standard CSS files to determine what code to modify (along with the syntax etc), before adding it to my custom CSS. I can't do that now, which is going to make any future additions to the custom CSS far more difficult for me to accomplish.
 

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

I agree that it would be much better to restore the ability to edit CSS templates.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

I also cannot believe that you've removed this, and, after more than 15 years, and also looking at alternative boards to import my site into...totally unacceptable!
Your site speed is absolutely horrid...the only way I've been able to make my site get even average speed scores has been through extensive modification of CSS--now you've removed this ability from my--WHY??!!

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

That's great, thanks. Is there a full record of the default CSSs available somewhere for reference purposes?

Thank you.
Going forward, maybe the best solution would be to have all CSS showing but read-only, with the ability to revert if differences are found?

That's fair. I can add this to our development documentation.
I'm working on an upgrade step to resolve this. 👍

Not recently, but I have now no way of comparing the two versions to see what's going on and no way of reverting if something is amiss. That's a bit of a setback and more of a 'downdate' than an update.
I have always used the access to the standard CSS files to determine what code to modify (along with the syntax etc), before adding it to my custom CSS. I can't do that now, which is going to make any future additions to the custom CSS far more difficult for me to accomplish.
 

In addition to this, check your server error logs at times just before this starts to happen. Its likely you will see what is the underlying cause of the problem there

I would need more information on this. How is it you have removed permissions? If you havent already, you should really remove permission at a module level from the content discovery module
https://invisioncommunity.com/4guides/how-to-use-ips-community-suite/managing-members/member-permissions-r305/