Archives are only one page deep
-
Before I try #1, I’d like to ask a question. On the old customizer, it was possible to save all the current blog settings (I think it was called a snapshot) so we could easily reload an old design if something went wrong with any revisions. Does that option still exist somewhere?
You’re right, that was a feature called Snapshops, but it was retired last year.
You can still see the CSS Revisions option for looking at old CSS.
Thanks for confirming #2-3.
#4 – when you used your phone, did you use the same Wifi network as in your home, or a cell network? So to confirm, the correct font displayed on your phone, right – Kreon? So the issue is only on your desktop/laptop machine?
-
Sorry about that error earlier. Let me straighten things out.
The phone was using a cell network. I did a second try just now with the phone and got Ubuntu. Kreon displayed the first time (the instance I reported a few minutes ago).
Ubuntu is the font that should be displaying. Kreon is the backup font (as you noted in an earlier comment in this thread) and it is also the theme’s default font.
-
What risk are you concerned with? There isn’t really any risk as you’ll just replace your CSS right after the test. :)
-
That’s what I was trying to explain earlier. My experience with the CSS editor was not good. I would try the “copy and paste everything back in” when I was developing this design and it didn’t work, at least some of the time. That’s why I had to play around with what order I entered the lines. If something goes wrong again, I don’t think I remember the tricks well enough to get the layout back up.
(BTW: This is the only CSS I’ve ever done and it was with a good amount of help. That means I lack the skills to perform any fixes that might prove necessary.)
-
That’s why I had to play around with what order I entered the lines.
Yes, the order of CSS does matter thanks to something called CSS inheritance. :)
I have made a copy of your custom CSS in my own text editor and will save it for you if you’d like to go ahead with the test – it’s up to you. You will also be able to revert back to your previous CSS by clicking the CSS Revisions link.
I will also post it right here for you for posterity.
.content .page, .archive .post, .search .post { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide1tall-e1398093466606.png') 10px top no-repeat; padding-top: 148px; } .post-top, .format-aside .post-top, .format-standard .post-top, .sticky .post-top { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide1tall-e1398093466606.png') 46px bottom no-repeat; min-height: 163px; } .post-title { max-width: 475px; margin-left: 35px; } .post-middle { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide2mm-e1398091600699.png') 35px top repeat-y; position: relative; left: 11px; } .page-content { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide2mm-e1398091600699.png') 0 top repeat-y; padding: 0 50px 20px; position: relative; left: 10px; } .post-bottom { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide3bb-e1398091576442.png') 45px -3px no-repeat; min-height: 86px; } .page-bottom { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide3bb-e1398091576442.png') 10px -3px no-repeat; min-height: 86px; } .wf-active .archive-title { position: relative; top: -30px; left: -30px; color: rgb(0,0,255); } .single-post-title h2 { position: relative; left: 0; color: rgb(0,0,255); text-align: center; padding-bottom: 20px; } .page-title a { position: relative; top: -50px; text-align: center; text-decoration: underline; font-size: 30px; line-height: 120%; } .post-title a { text-align: center; } div.widget.image-2.widget_image { position: relative; left: -3px; } .sidebar-top { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide1rt-e1398083880430.png') no-repeat scroll left center transparent; } .sidebar-middle { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide2rm-e1398091794656.png') repeat-y scroll left top transparent; } .sidebar-bottom { background: url('http://bumblepuppies.files.wordpress.com/2014/04/slide3rb1-e1398091993839.png') no-repeat scroll left top transparent; } .sidebar-top { min-height: 120px; } .sidebar-bottom { min-height: 125px; } .widget h3 { color: rgb(0,0,0); border-bottom: 1px solid rgb(167,219,216); box-shadow: 0 1px 0 rgb(255,255,255); text-shadow: 0 0 0 rgb(255,255,255); } .post-title a,.page-title a { color: rgb(0,0,255); text-shadow: 0 0 0 rgb(255,255,255); } .widget ul { color: rgb(0,0,0) !important; } .page-wrapper { text-shadow: 0 0 rgb(255,255,255); } h1, h2, h3, h4, h5, h6 { color: rgb(0,0,0); text-shadow: 0 0 0 rgb(255,255,255); } .sidebar-top { position: relative; left: 20px; } .sidebar-middle { position: relative; left: 20px; } .sidebar-bottom { position: relative; left: 20px; } .post-title { line-height: 180%; } .nav-menu a { display: none; } .widget h3 { color: rgb(0,0,0); border-bottom: 0 solid rgb(167,219,216); box-shadow: 0 0 0 rgb(255,255,255); text-shadow: 0 0 0 rgb(255,255,255); } .wf-active .widget h3 { font-weight: bold; } .sidebar-content { left: 15px; } .widget ul { font-weight: bold; margin-left: 25px; } .search-input { color: rgb(0,0,0); width: 90%; } div.widget.search-2.widget_search { position: relative; left: 5px; } .widget h3 { font-weight: bold; font-size: 20px; } .archive-title { position: relative; top: -30px; left: -30px; color: rgb(0,0,255); } .post-date { padding-bottom: 10px; text-align: center; } .comment-author-name, .comment-author-name a { color: rgb(0,0,0); } .reply a { color: rgb(0,0,0); } ul.children .comment-wrapper { background: none repeat scroll 0 0 #99ccff; border-left: 10px solid #0099cc; border-top: 10px solid #0099cc; BORDER-bottom: 10px solid #0099cc; border-right: 10px solid #0099cc; } ul.children .comment-body, ul.children .reply-wrapper { background: none repeat scroll 0 0 rgba(142,180,227,0); } .comment-wrapper { background: url('http://bumblepuppies.files.wordpress.com/2014/04/commentt-e1398114671968.png') no-repeat scroll left top transparent; } .comment-body { background: url('http://bumblepuppies.files.wordpress.com/2014/04/commentm-e1398114620572.png') repeat-y scroll left top transparent; } .reply-wrapper { background: url('http://bumblepuppies.files.wordpress.com/2014/04/commentb-e1398114502338.png') no-repeat scroll left top rgba(0,0,0,0); min-height: 70px; } .wf-active .widget a { color: rgb(0,0,0); } a, a:visited { color: rgb(0,0,0); } .page-title a { font-size: 22px; } .wf-active #reply-title { font-size: 24px; color: rgb(255,255,0); } #comments-title, .nocomments { font-size: 30px; color: rgb(255,255,0); font-weight: bold; } .wf-active .archive-title { color: rgb(255,255,0); } .left a, .right a, .left a:visited, .right a:visited, .footer a:visited { color: rgb(255,255,0) !important; } #respond p.comment-subscription-form label, #respond label, #respond form label { color: rgb(255,255,0); } .nav-menu, .nav-menu a, .nav-menu a:visited, .nav-menu li + li:before { Display: none; } .post-top, .post-middle { padding: 10px 90px 0 65px; } .page-content { padding: 0 80px 20px 50px; } .wp-caption { max-width: 500px !important; } .post-bottom { position: relative; top: -20px; left: 1px; } div.grid-8 { position: relative; left: -25px; } div.widget.freshly_pressed-2.widget_freshly_pressed { position: relative; left: 6px; } -
You could also first try “commenting out” your CSS by putting these tags around the whole shebang:
/* */That should temporarily deactivate your custom CSS without removing it all, though it’s not as reliable a method as removing it, since if you had any internal comment tags within your CSS they may interfere, but it doesn’t look like you do.
-
As a side note, I noticed you’re referencing your image paths with a http:// link – that will give you mixed-content warnings about insecure items on the page, since we now serve up WordPress.com URLs with https:// only. You can fix that by removing the http: part, so for example, change
http://bumblepuppies.files.wordpress.com/2014/04/slide3bb-e1398091576442.pngto
//bumblepuppies.files.wordpress.com/2014/04/slide3bb-e1398091576442.png -
First a blanket “thank you” and then a specific “thank you” for the tip about losing the http. I’ll be taking care of that in the next day or two and I would have never thought of it.
Anyway, I went through the process twice. (Twice because I forgot to close Firefox the first time, which also clears the Firefox cache.) I did both tests in Chrome with an empty cache. Both times, Kreon displayed when I initially loaded the page. And, both times, Ubuntu displayed when I refreshed the page after it had finished loading.
-
First a blanket “thank you” and then a specific “thank you” for the tip about losing the http. I’ll be taking care of that in the next day or two and I would have never thought of it.
You’re welcome on both fronts.
Both times, Kreon displayed when I initially loaded the page. And, both times, Ubuntu displayed when I refreshed the page after it had finished loading.
Thanks for testing this in Chrome. It’s normal that you’ll only see Ubuntu when the page finishes loading, because that font is being loaded from Typekit’s server, and so the site’s connection to Typekit must be fully completed before you’ll see Ubuntu in effect on your site.
-
I don’t expect Ubuntu to show while the page is loading. Kreon showed when the page was completely finished loading. As I said (and as you quoted me on saying), Ubuntu did not show until after I reloaded the page on each attempt. The first fully completed load showed Kreon at the end.
-
You’re right – I missed the word “refresh.”
I had another theme wrangler take a look at this they had no troubleshooting ideas that we haven’t already tried, and they too were able to see the Ubuntu font correctly on your site’s first page load.
The next step at this point would be to try another computer in another location, like a library. I understand your anonymity concerns, but that would be what I recommend at this point. There’s no need to log into your account, and you could use an incognito browser window. Let me know if you decide to go that route.
-
Right now, i am doing the best i’ll be able to do. I cleared my phone’s files/restarted and am away from the wifi that’s at my usual location. Phone was supposed to be disconnected from wifi the first time, but maybe something was off. Anyway, no access to wifi here, did not get mobile theme, and my phone displayed kreon. I only viewed the homepage and only once.
-
Gotcha! If we think of anything else to ask you to try, I’ll let you know. I realize this must be frustrating, these sorts of intermittent issues can be super tricky to diagnose.
- The topic ‘Archives are only one page deep’ is closed to new replies.