• updated base code to fix overlapping on audio posts without album art, simplified post info CSS, deleted a bunch of dead CSS
• fixed issue with caption and username margins on lilac on certain npf photoset/photo and regular photoset/photo posts
• new fade-in loading animation on holly so posts won’t overlap each other before all of the content has been loaded

this is a follow-up post for two issues that people have messaged me over the semester about: BROKEN NPF PHOTOSET SCRIPTS and problems with the ASK AND SUBMISSION BOX HEIGHTS NOT RESIZING PROPERLY. if you have either of the above problem, please read this. if you are also have issues with broken scripts (e.g. TOOLTIPS OR DROPDOWNS NOT WORKING), please read this.

I’ve updated my themes to correct the latter error and I’ve deleted the script that converts NPF photosets to regular photosets from my themes. tl;dr: if you’re using one of my themes, please update your theme from my pastebin or my github. if you’ve installed lilac or rosemary from the theme garden, you do not need to manually update; when Tumblr staff approve my code changes (hopefully in a few days, but it could be a week or two), you’ll get the update automatically. if you want to update your themes manually, skip to the read more.

the NPF photoset conversion script got broken because Tumblr changed how they code NPF photosets, and when I checked it out on a bunch of my test sideblogs, the NPF photosets frequently display with different coding, even when the blogs all have the exact same theme. I’m guessing this is because whatever changes Tumblr’s making to NPF photosets and the new post editor haven’t been finalized. because of that, I’m not going to do anything about the NPF photosets coding in my older themes at least until they finalize their changes and implement the new post editor. 

I’ve also been thinking about my approach to theme making lately and I’ve decided to just give up on any stuff that attempts to revert new changes back to the way it used to be. I don’t have the time and energy to play Tumblr whackamole and come up with new coding every time something changes, so I’d rather work with the changes than against them. plus, not every change is a detriment. 

if you really don’t like NPF photosets, in the meantime, I’d recommend turning off “Use new post types” in your customization panel, not using the beta post editor, and/or trying glenthemes’s lovely conversion script. hopefully, sometime in the next few months, Tumblr will finalize their changes and release documentation for NPF posts so that us theme makers can style them properly.

instructions on manually updating my themes are under the cut.

Keep reading

a typo was causing the header and post container to break on blogs when the askbox was turned off. I’ve corrected it and updated the code, but if you installed anemone on Feb. 22, 2021 or Feb 23 (depending on timezone), you may want to update your theme from pastebin or github.

a user alerted me to an issue with the NPF photoset conversion script I use in all of my themes involving NPF photo posts containing both a video and a photo or photoset. the TL;DR version is that whenever someone posted an NPF photo post containing a video and a photoset, a syntax error I made when inputting the class names into the script was causing all of the scripts to break on my themes. 

this only applies to the updated versions of my themes; if you are using a version of my themes that doesn’t include the NPF photoset script (so probably anything installed before May or June 2020), it won’t apply.

update: as of october 19, 2020, all themes have been updated on pastebin and github, so please REINSTALL from there if you installed the theme prior to that date.

if you want to update your theme yourself, the fix isn’t complicated as long as you follow the instructions below closely and don’t delete anything important.

first: this script requires you to edit within the jquery section. it’s not hard, but if you’re totally unfamiliar with jquery syntax, you may want to save a backup copy of your theme before you do this. however, as long as you follow the instructions closely and don’t delete anything important or add anything extraneous, you will be fine. of course, you can simply reinstall the theme from my pastebin or github if you mess things up.

if you are using older versions of cherry blossom, wisteria, holly, bluebell, dahlia, or lilac:

go into the HTML of your theme and use ctrl + f to find this part of the code (it’s at the bottom):

undoPhotoset({
       'posts': '.text-post',
       'text class': '',
       'photoset class': ''
   },false);

and delete it.

copy and paste this:

<script>
undoPhotoset({
        'posts': '.posts .text-post', 
        'text class': '.text-post', 
        'photoset class': '[photoset-layout]' 
    },false);
</script>

and put it right above <script>. on holly, put it immediately above <script type=“text/javascript”>.

if you are using older versions of nightshade, celandine, moonflower or honeysuckle:

go into the HTML of your theme and use ctrl + f to find this part of the code (it’s at the bottom):

undoPhotoset({
       'posts': '.text-post',
       'text class': '',
       'photoset class': ''
   },true);

and delete it.

copy and paste this and put it immediately above <script>:

<script>
undoPhotoset({
        'posts': '.posts .text-post', 
        'text class': '.text-post', 
        'photoset class': '.photo-slideshow' 
    },true); 
</script>

thanks to @eggdesign​, i have a fix to stop new tabs from appearing at the bottom if the viewer scrolled down on the previous tab, which an anon from yesterday mentioned. the code has been updated on both my pastebin and github, so you can reinstall from there. if you want to add the fix yourself, go below the cut for instructions:

Keep reading

after looking at it some more, i figured out exactly what was causing the popup in dahlia to appear out of place in other browsers: i put position: fixed; on the wrong selector! i’ve updated it again on pastebin and github and tested it in other browsers, so it should work fine in any browsers. and now there’s no ugly queries to force it to do different things in different browsers, so the code looks much nicer.

with my newest theme holly, on some blogs, the feather icons script seems like it isn’t loading correctly on the first blog page, while on other blogs, it seems like it’s loading just fine. so for some people, the like and reblog buttons aren’t showing properly on the first blog page. i’ve replaced the icons with the svg versions, so hopefully that will fix this particular bug.

if you’re using the theme and your like and reblog buttons aren’t showing up on the first page of your blog, you can go and reinstall holly from my pastebin or github. if the icons are showing up fine for you, don’t worry about it, but if you want to, you can reinstall just to be safe.