Archive Questions

Ah, okay, I figured out the Collection link part of my question. I just realized that it’s the first line of options in the Template Options allows you to change where it points to. I switched from ‘an archive page’ to ‘the first webcomic’, which I’m satisfied with.

Still haven’t figured out where the line break in front of the Collection title is coming from though.

Looking closer at the issue and I don’t think it’s actually a line break. It looks more like the line height is just too tall for the text. However, when I use a taller graphic instead of text, it still has that vertical offset so I really don’t know.

Not sure what to do about this yet. I’m guessing I should look at the template file to fix this? (Sorry, WordPress newb here.)

G.

I was playing around with some of the webcomic short codes for setting up an archive page and I’m seeing the same line offset. For example, [webcomic_list_collections] renders the line exactly the same way as the Archive Templage, with the Collection line appearing to be on the next line after the bullet. I’m guessing this is a bug?

G.

Here’s what I mean:

View post on imgur.com

This is using Storyline instead of Collection and you can still see the vertical offset from the bullet image. I was clicking on the link when I made this screencap, which reveals the item (about 48 pixels tall) that raises the height of the line right after the bullet.

Is there away to remove that item or correct it’s height so the Archive text lines up properly with the line?

On a slightly separate matter, is it possible to hide the bullets? If I’m using images, it seems unnecessary to show bullets.

Thanks in advance for any help or information.

G.

Hi Greenlaw,

I’m not sure about the vertical spacing –?I can’t seem to replicate it on my dev box – but you could try adding something like this to the theme style.css file:

ul.webcomic-collections { /* removes list styling */
  list-style: none;
  margin: 0;
  padding: 0;
}

ul.webcomic-collections a {
  line-height: 1.2; /* default line-height in most web browsers */
  margin: 0; /* just in case */
  padding: 0; /* just in case */
}

Thanks Michael!

So far I’m not getting it to work as expected but I’ll keep poking around with this some more.

G.

BTW, I think I was wrong…the bullets do help. Since the strip are b&w, the small ‘thumbs’ of kinda ‘blend’ together as one without the bullets.

So, now it’s really just second bit of code (for the long vertical white space I’m trying to get working.

Also, since you’re not seeing this issue on your system, I’m going to try a clean install on a different computer and see what happens there. Will let you know how it goes.

G.

Ah, I got first part of the code working. Duh! I had forgotten I switched from Collection to Storyline. Changing to Collection with this code did remove the bullet from the main Collection name.

I tried changing the code to ul.webcomic-storylines, thinking it would do the same but I guess it doesn’t work that way. Will come back to this later.

I still can’t get the second part working at all.

G.

Ah, I got it!

I changed ‘webcomic-collection’ to ‘webcomic-terms’ and bullet disappeared from the Storyline name.

This also seems to solve the vertical line problem since, as you noted, without the bullet the line shouldn’t be there.

Thanks Michael. If you have any questions requests for me for further troubleshooting, let me know.

Argh! This code is working for removing the white space in the Storyline name but it’s also breaking the ‘drop-down’ icon for the menu bar.

ul.webcomic-terms { /* removes list styling */
line-height: 1.2;
list-style: none;
margin: 0;
padding: 0;
}

Here’s what the menu ‘drop-down’ arrow looks like with the code:

View post on imgur.com

I guess this means I can’t use ‘terms’ to fix this for the Storyline option.

It’s always something isn’t it? (At least I’m learning a lot of new stuff along the way.) ??

For now, it looks like I need to either switch back to ‘Collection’ with the originally posted version of the code, stick with ‘Storyline’ and live with the tall vertical space after the bullet, or just create a regular page and manually update the archive.

I know it’s kind of a small thing but it’s making me a little nuts. I think I”m going to put this aside and think about it while I work on some other stuff.

Michael, since you’re not seeing the error on your end, I think I might leave out code and temporarily migrate to the actual remote server and see what the site does there. If it works fine, it may confirm that the issue is unique to my local install and maybe I should worry about it. Will let you know how that goes.

In the meantime, if you or anyone else here has of a suggestion, let me know when you get a chance. Thanks!

G.

Quick update: The above post is slightly inaccurate.

I switched back to Collections pasted in the original ‘Collections’ version of the code and it seems to break the menu ‘drop-down’ arrow too. I guess the Menu is the same formatting as the Archive. Maybe I need to change something it the Menu setup?

Anyway, I said I’d put this aside so I guess I should move on for now. ??

G.

Hold it!

I decided to check one more thing before moving on.

I had compared the style.css from a clean Inkblot file to the one that’s giving me the broken ‘drop-down’ arrow. The only difference I could find was the added code…however, if I remove the code and use the ‘cleaned up’ current file, I still get the broken arrow. But if I replace the ‘cleaned up’ style.css file with the original, actually clean style.css file, it works fine.

To me this suggests that something else is different between the two style.css files that I can’t see in my text comparison tool, or perhaps the current file itself is slightly corrupted.

I feel I’m getting closer to figuring this out. I’ll post more info after I take another look at this tonight.

G.

Thanks for the updates Greenlaw, and apologies for not being more help along the way. Glad it’s sorted now!

Edit: Oops; that’s what I get for replying based on an older alert email (and also not keeping up with my email).

The code you added shouldn’t have had any effect on the menubar icon…?it looks like the wrong font is being used for that icon, actually, or the web browser is misinterpreting which font it should be using. Those icons use FontAwesome glyphs, all of which are outside the normal character range. I’d double check to make sure the the correct @font-face declaration is in style.css (it should be right near the top; it’s pretty hard to miss):

@font-face {
  font-family: 'awesome';
  font-style: normal;
  font-weight: normal;
  src: url("https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/fonts/fontawesome-webfont.eot");
  src: url("https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/fonts/fontawesome-webfont.eot?#iefix") format("embedded-opentype"), url("https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/fonts/fontawesome-webfont.woff") format("woff"), url("https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/fonts/fontawesome-webfont.ttf") format("truetype"), url("https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/fonts/fontawesome-webfont.svg#fontawesomeregular") format("svg"); }

Once again, thank you Michael! You’re input is very helpful.

I’ll check the code again tonight to be sure that’s all it is. I responded to you personally just a few minutes ago but I’ll post a short version here for anyone following this thread.

If the font code checks out and I’m still seeing problems, I’m going to try replacing Inkblot with a clean copy or maybe even reinstalling WordPress from scratch.

Working with WordPress this past month has been a learning process for me. There has been a lot of experimentation with various plug-ins and code tweaking so I guess it shouldn’t be too surprising that I’m seeing some weird behavior now. Naturally, I’ll lose some data by starting over but to be honest, I’m not so far along that it’s going to be all that difficult recreate the site if I make a few screencaps. Plus, I’ll gain some peace of mind knowing that file corruption is less likely to be causing these unexpected problems.

I’ll post again tonight with my progress.

Aha! I found the error. It was at the very tippy top of the page in fact. In the current file, the first line is [Fe@charset “UTF-8”;] but it should be [@charset “UTF-8”;]. Removing the Fe fixed the menu icon problem.

I’m not sure how I missed that when even my file compare program flagged it. I guess I really needed to step away from this project for a day.

Thanks again for your help Michael.