varpness
Forum Replies Created
-
In case anyone else reads this later, it turns out I need to add a few font size lines to the areas in which I needed to change. I basically increased the body font size (in this case I converted it from px to em). This made everything bigger, so I went into the individual tags and added a font size: 0.6em line which shrunk the parts that I didn’t want to be so big.
I hope this helps future visitors who are working with the same theme.
I kind of thought this would be difficult, because I can generally figure this stuff out on my own. It looks like I might need to add a font size tag for the line specific to my post content body, but I’m having trouble locating it.
Is it preferred that I post my css directly into this thread, or is my link okay?
Okay, I see what you’re saying. Thank you for educating me on that subject. ??
I’m taking the website out of maintenance mode so you’ll be able to see how the cascading works. Thank you for looking into this for me.
The address is https://varpness.com
I have it in maintenance mode right now so visitors are not confused. I posted a picture of the website and the stylesheet file, so I’m not sure how the actual website would be any more useful. Perhaps I am just ignorant though.
Forum: Themes and Templates
In reply to: &.#8220; instead of a quotation markHmm, it’s not just the quotes. Anything that is not a normal alpha-numeric in the second paragraph gets changed into something weird. For example, I have just a regular carriage return, and it puts these boxes in place. It only happens to whatever starts the second pargraph.
https://varpness.com/quotes-from-me-that-should-be-famous
This is where you can see the weird boxes.Forum: Themes and Templates
In reply to: &.#8220; instead of a quotation markActually, I sort of did a work around to the problem by having a line break at the beginning of the post. So actually it’s not fix, I just couldn’t figure it out so I cheated.
Forum: Themes and Templates
In reply to: &.#8220; instead of a quotation markThis is the section with the drop information. For some reason it was “dropping” or making the first letter large on the first letter of the second paragraph, so I just used the /* tags to ignore the “.drop” which solves the issue of having it make the first letter of ever second paragraph big. But even if I keep the drop in there, it still does the 8220 thing. What am I missing here?
/* ———————————– post meta */
.meta{display:block;list-style-type:none;list-style-image:none;margin:20px 0;padding:5px 0;font-size:11px;}
.postspace{background:transparent;width:80%;height:32px;margin:0;padding:0;}
.rel{float:left;width:48%;margin:0;padding-right:20px;border-right:1px solid #333;}
.pro{float:right;width:44%;margin:0;padding:0;}
.drop{float:left;font:3.5em century gothic,tahoma;line-height:100%;margin:3px 8px 0 0;width:30px;text-align:center;}
.social{clear:both;height:24px;width:99%;padding:13px 0;font-size:11px;color:#666;}
.social a{color:#666;text-decoration:none;margin:0 13px 0 0;}
.social a:hover{color:#000;text-decoration:underline;margin:0 13px 0 0;}Forum: Themes and Templates
In reply to: &.#8220; instead of a quotation markThank you so much for your help stvwlf! I’m going to give it a shot right now!
Forum: Themes and Templates
In reply to: &.#8220; instead of a quotation markHere’s the problem.
https://varpness.com/archives/367Forum: Themes and Templates
In reply to: &.#8220; instead of a quotation markI guess links are not allowed because it deleted my link (I’m not sure why we have a link button). But I think you guys get the idea.
Forum: Fixing WordPress
In reply to: Specified file failed upload test. – Can’t upload images!Do not post link to unrelated topics. This is not the same issue, and I am not using any plugins, so deactivating the Bad Behavior plugin is irrelevant.
Forum: Fixing WordPress
In reply to: Image upload failsDon’t post link to unrelated topics. This is not the same issue.
Forum: Fixing WordPress
In reply to: Specified file failed upload test. – Can’t upload images!Yes, I am having the exact same problem. For some reason, RC1 gives me the same error message but I can see the images. RC2 and 2.5 final won’t even let me see the thumbnails.