I did have the debugging mode set in one of my test sites and some of the errors pointed to a compiler and scss file - but I did not have time to take a screen shot. When I tried to change the debugging mode I got the error message above
The ‘Consider Warnings as Errors’ setting has resulted in what you are warned about in the red text. You will need to edit the config key in /application/config/concrete to clear it.
Hi thanks for the tip. The problem with the error settings only occurred in my test sites. I tried looking at /application/config/concrete.php but I could not see anything that looked like a “key”. Anyway irrelevant now I can easily re-install the test site.
My production site is still working ok - but the problem is I cannot edit the skin customization tab (see top screen shot) Can anyone help with this ?
I found these error messages in the logs if they are relevant ?
Exception Occurred: /home/meg/public_html/updates/concrete-cms-9.2.4-remote-updater/concrete/vendor/illuminate/filesystem/Filesystem.php:57 File does not exist at path /home/meg/public_html/application/themes/atomik/css/presets/default/_customizable-variables.scss. (0)
Exception Occurred: /home/meg/public_html/updates/concrete-cms-9.2.4-remote-updater/concrete/vendor/illuminate/filesystem/Filesystem.php:57 File does not exist at path /home/meg/public_html/application/themes/atomik/css/presets/default/main.scss. (0)
I managed to revive my test site by editing out the complete section on debugging in /application/config/concrete.php.
Unfortunately the issue of debugging has turned out to be a red herring in this post, I apologize for causing this problem.
On my revitalized test site I managed to take a screenshot of the full error message of the custom skin editing page which does not work this was the intended main issue of this post
From your debug screen, scroll down the top left panel to the bottom of the section until you see [COPY] and copy the debug trace into your PC clipboard.
Then, please either add your trace as a new post in the existing GitHub issue, or create a new GitHub issue. Also add your other evidence such as the screengrabs above.
That won’t provide an immediate solution, but may help the core team find a solution for the next monthly core update.
You might be using a skin built with an older version of Bedrock with a new version of Concrete? I know those issues don’t happen in the new version of Bedrock:
I am using the standard Atomik theme starting with version 9.1.3, and it has been updated to 9.2.4
I used only customization (colours, fonts etc) from the Atomik/Concrete backend. I did not introduce any code from anywhere , just using the facilities available in backend .
My production site is the same, no page templates. I have tried adding templates in the backend
Dashboard>Pages&themes>Page Templates “add templates” but with no results.
Should I copy the pages from /concrete/themes/atomik/elements and paste ? If so where to past ? There is a directory /application/page_templates but this completely empty and there is /application/themes/atomik/elements which contains the footer.php files ?
I thought I might round off this post as I have found a solution.
To recap I had three sites, a production site which has been on line for about 1 month and 2 “test sites” on my local computer all based on the Atomik theme with the same custom skin.
The problem was that the custom skin facility in the standard Atomik theme stopped working and it was not possible make any changes to the customs skin as there was error (detailed above)
Also there were no page templates listed under the atomik theme, on all 3 sites.
On one of my tests site I tried I copying the page templates from /concrete/themes/atomik/elements to application/themes/atomik/elements - this worked on the test sites the list of available page templates reappeared in the Atomik theme (although it was still not possible to edit the customs skin). The same procedure did not work on my production site.
On all three of my sites it was possible to make and edit a custom skin with the Elemental theme.
My solution to this problem was to buy the Subatomik theme from the Concrete marketplace.
The installation went without problems, the transition was easy, and I had details of my original custom skin, so it took only a few minutes to recreate a replica of my original skin, hence very little down time.
