tobbexiv
commented
5 years ago Hi humantex,
from your description I cannot find any mistake you could have made. Thus, it is quite hard to find the issue here. Is it possible for you to mail the *.zip file you created to my contact email adress (it is listed in the composer.json)? Then I would check and debug it directly in my own test system.
Thank you and best regards, Tobbe
I just got around to revisit modifying the admin style, and tried your example. I thought I'd try to use it with your default settings first - to replace the pagekit default 'theme.css' with a heavily modified 'theme.css' - by only adding the css folder (now holding that new css file) and not making any edits to index.php. That didn't trigger anything, and the css remained the same.
I'm assuming that I've read and understood your notes, so if it's obvious that I missed something, let me know. I had no problem toggling the extension on/off, so there was no apparent issue in file/folder placement of the extension itself.
I then tried to modify both the new css file name itself, and the entry in index.php to match it (i.e., theme-custom.css), and again, no change in style after a page refresh.
I completely disabled the site cache, and cleared it and the temporary files before each attempt. In FireFox dev tools, the network output confirmed a fresh '200 get' with each page refresh to retrieve every file required, and showed no errors in the console. Dev tools styling editor also showed no change to the called path for admin css files to anything but the default.
I reset everything and enabled Pagekit's debug mode, and found no errors or log entries on 2 new attempts. There was only 1 call showing in the 'events' listing in debug, and I'm posting a screengrab to show details.
I haven't yet tried to use the extension to add a secondary css file to modify the style instead of replacing the default, but I'll let you know the results when I've had a chance to run through it.