1.) Profile Cover not visible on android phone and pc. A fix is to reposition if you have a profile cover like these one below. :)

2.) Profile Cover cannot be deleted after clicking these buttons

Thanks for your reply ~Z~ Man. As of now that's what i have notice in my GreenByGreen Theme :)

Tagolan,
Background image? Delete button? I have no idea what you're talking about. Please send a screenshot and stick to the rules of How-to-report-a-bug.

Hi somehow background image will appear and sometimes doesn't. I could not also delete background image when pressing the delete button, it will prompt you to delete after that nothing change.

V 2.3 comes with backup / restore mechanism now - see detailed description in the beginning.

Thank you for your feedback, Sarah.

And yes: I was already thinking about some kind of backup mechanism, but it's still not quite complete.
Starting with V 2.2, the relevant css files are copied to a GreenByGreen subdirectory in your ossn_data tree WHENEVER you disable GreenByGreen - that is when you switch to a different theme.

Thus, theoretically you could install a GreenByGreen update and copy those saved files back in place.
Sounds smart at first sight, but what if the update comes with its own necessary changes? You would either blindly overwrite them or had to manually merge them. Still not foolproof ... and in a way counteracting my original idea of easy customizing. :)

Thank you,

Might there be a way to save settings (other than saving the pdf files) during the next update?
Maybe an import/export option?

Restoring my logo and color scheme only took a moment, but I didn't expect to lose those settings when I upgraded.

I did upgrade via the panel, mhaps if I did it manually that may have saved it?

Thanks for your hard work!
It's a great theme and I love being able to customize most of it without the need to dig in the filesystem. :)

Thank you

Due to the built-in color-editor the structure of the 2.x release is very much different compared to 1.x.

Right that's why I placed the blue emphasized 'not compatible' note on top.

Looks like good changes. My question is, what would be the best method for preserving my changes in site.php? My changes are extensive, so it is obvious I will need to do this on the development server, but is the structure still similar enough that I could cut and paste the changes I made on the old site.php to the new one, or do I have to start from scratch?

V 2.2 comes with paperplane submit icons in comment fields now:

And that means:

• the Enter button is working the same way as in posts and other text-areas
• no more trouble composing posts with newlines on touchscreen devices