apologies for this one, I’m about to embark on my first steps into custom css for a module.

it’s a simple addition, but where do I put the modification, does it go in the css folder within the individual module, or the custom.css file within the main css folder in the MagicMirror directory?

I want to add this,
#GPHOTO_CURRENT {
background-size: cover;
}
as a change to MMM-GooglePhotos.

I have a very strong feeling its the latter but don’t want to mess this up, this feels like the movie Inception, I’ve only been in the first level of the dream and this is the dream within the dream.

cheers.

is that not the file it asked me to rename in step 9?
Nothing has downloaded following steps 10 and 11.

@sdetweil Hey, it worked today, I guessing I was trying to do everything too close together and not giving it time.
In the setup guide step 12 says,
Copy the file token.json and credentials.json to the folder MMM-GooglePhotos in the remote device

where am I copying those from?
when I go into the GooglePhotos folder on the Pi those 2 files are already there, do I assume those are the onces it wants me to copy?

Working through the install guide found here,
https://github.com/hermanho/MMM-GooglePhotos/blob/master/INSTALL.md

got to step 10 it opened the browser as expected, I click on the same email address used to set everything up with Google but I get,

Access blocked: MagicMirror photos has not completed the google verification process.
email addressed used

MagicMirror Photos has not completed the Google verification process. The app is currently being tested and can only be accessed by developer-approved testers. If you think you should have access contact the developer.

if you are the developer of MagicMirror photos, see error details.
Error 403:access_denied.

I’m pretty certain after following a step earlier it said verification wasn’t necessary.
I only went through the steps for this install an hour ago, is this something I need to give time to?

sorry this is a little vague, I’m doing some of these steps on the pi itself and it is painfully slow but if anyone can shed some light on where I should be looking that would be cool. I’ve never had to deal with Google in more than a search capacity.

Cheers.

@sdetweil new install of MM is one the new SD (failed the first time so had to run again and seemed to take a while).

when I run your backup script will it automatically find the previous MM install on the old SD card mounted with USB?

if not how do I get it to find the previous install to copy the files I need?

@sdetweil so I’m not manually moving the config and CSS files myself that will be done after via terminal?

@sdetweil right so when I copy those 2 file’s am I literally just dragging a copy to the new SD’s home screen (just so they’re on the new card) or do they need to go into a MM specific folder on the new card.

I can find both of those files on the old SD but I’m not understanding from

ls >~savedlist.txt.

am I doing that after I’ve installed a fresh MM on the new SD card once that MagicMirror/modules folder exists because running the above command won’t work as the new SD has no reference to MM’s existence.

@sdetweil So install the base of MM on the new SD then follow the steps in your previous post?

I have a feeling it definitely won’t be that easy.

@sdetweil hey Sam, I can still see the old list of modules on the old SD card.

If that’s the case can the old card still be used?

the new card is just a completely empty Pi OS, nothing to do with MM on there yet.

Do I need in run the basic install for MM on the new SD to get that running?

had a little crack at this again, the Mrs is bugging me to get “her” mirror back up and running.

So I’ve run sudo umount /dev/sda1
sudo umount /dev/sda2

Both drive folders from the mounted (old) SD disappeared from the home screen on the pi as expected.

then run, (and got)
sudo e2fsck -f -v /dev/sda2
e2fsck 1.46.2 (28-feb-2021)
rootfs: recovering journal
superblock needs_recovery flag is clear but journal has data.
Run journal anyway ? YES
e2fsck: unable to set superblock flags on rootfs

rootfs: *********** WARNING: filesytem still has errors *********