starwag
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Input Field and Button Spacing problemsThanks bcworkz. I was making tiny adjustments before, but felt I was going wrong by doing so. I will continue altering by increments. Not sure why the 100% is wonky either. However, since you mention it, I may go back and review the containers and sidebar above the codes here to see if something is altering how the percentages for my search box. Thanks again. You are always so helpful!
Forum: Fixing WordPress
In reply to: Input Field and Button Spacing problemsI have been altering the code, per the theme’s original intention, to simply provide a base for people to learn and work from. I have been learning code and theme development for the last 4 years through this theme. However, the CSS, and much of the code I am using, is all mine, regardless of the theme starting off as HTML5Blank. The original theme is stripped down immensely simply for this purpose. In truth, there may not be much of the original code left. The error would be on my end, so there is no point in asking for support form the original creator of the theme. The only reason why I have not altered the original credit is because there are still some strips of php in the functions section which I have yet to remove, and which belong to the original content.
Forum: Fixing WordPress
In reply to: Input Field and Button Spacing problemsIt should be noted that the above code only works if you resize the window to a much smaller size, less than 720px. Also, I have played with the code so that it is currently working with left and right floats, and the widths at 88% on the input field, and 10% on the button. However, if I resize this too small, the button jumps down to the next line. Conversely, if the screen is widened too much, the button separates form the input field. Ideally, the two should be beside one another at all times with no space between them, no matter how the screen is resized.
Forum: Fixing WordPress
In reply to: Distorted Website on MozillaThanks for the help guys! Since the problem seemed to be CSS and was largely on Mozilla, MS Edge, and IE, I went to Mozilla’s site to see if there was anything about CSS specific to them. I found a link to W3C validator, which I have never used before, and showed me exactly where the errors were. As it turns out, my calc() values were crammed too closely together, and Chrome was just being very forgiving. I can’t believe I have made it all this way without ever having used this! Now I’m wondering what other tools I haven’t been exposed to that could make my life a little easier. Thanks again!
Forum: Fixing WordPress
In reply to: Distorted Website on MozillaGeorge, I appreciate your praise and your honesty. Admittedly I have neglected Microsoft Edge and Internet Explorer, and haven’t checked Mozilla in a while, but I definitely have been checking it constantly on an iphone, an android, various tablets, Opera, and Chrome, and don’t see any of the design issues you are seeing. I have some things still marked as private, which is disturbing the design a bit, but once pictures are loaded and the posts are made public this goes away. If you are seeing something more drastic let me know, because then I’ll know I have another problem to address: why I’m not seeing what another person is seeing.
CrouchingBruin, I removed the offending JS, which doesn’t seem to make any difference to the Mozilla problem. The stylesheet on the 1.5 version of the theme I just downloaded appears to have the same 1.4.3 description at the top, so I’m assuming not much has changed there.
Is this likely CSS? I don’t come from a level of experience to say whether or not this problem is likely linked to CSS. I feel it probably is, but couldn’t say for sure.
Thanks for both of your responses so far.
Forum: Fixing WordPress
In reply to: Alignment in PostThanks for trying to help, but I discovered I was missing some essential CSS that works with WordPress. For anyone else out there who has similar issues, and is working on their developer skills, the code below is what you absolutely need in your theme’s stylesheet for images to work. Rookie mistake, but definitely available in WordPress’s Codex, which includes lots of other essential info. It took a bit more digging. You can find the codex here WP Codex I hope this saves someone else some time.
img.alignright {float:right; margin:0 0 1em 1em} img.alignleft {float:left; margin:0 1em 1em 0} img.aligncenter {display: block; margin-left: auto; margin-right: auto} a img.alignright {float:right; margin:0 0 1em 1em} a img.alignleft {float:left; margin:0 1em 1em 0} a img.aligncenter {display: block; margin-left: auto; margin-right: auto}Forum: Fixing WordPress
In reply to: Form Pushing Div Position OutThanks for the help! display: flex seems like it is going to work.
Also, I changed the http: info to https: but the view on mozilla is still messed up. I thank you for pointing it out to me, though, as I had not checked the website view from there in a while. However, I will be opening another question, as I don’t really know how to fix the problem.
Thanks again.Forum: Fixing WordPress
In reply to: Alignment in PostDoes anyone have anything helpful to add to the question I asked?
- This reply was modified 7 years, 3 months ago by starwag.
Forum: Developing with WordPress
In reply to: Search Results Cut ShortThe CSS solution did help with cutting the results short. However, I’m going to mark this as answered and address the other half of this issue in a separate posting. I feel I am getting into something different than just the search results getting cut short, and no one else is going to get the benefit of the solutions if I bury them in this thread. Thanks again.
Forum: Developing with WordPress
In reply to: Search Results Cut ShortWhat I mean is, if I chopped down my search.php file to just be the gray box, and then used AJAX to load the search.php in place of the gray blog feed box on my single post page, would that still necessitate using get_post(), or could I avoid having to use it? My goal was to eventually load search results in place of the blog feed on any page without having to refresh, which means I won’t know what post or page someone is clicking/reading when they decide to use the search form.
Forum: Developing with WordPress
In reply to: Search Results Cut ShortWould using AJAX to load the search results keep the results from replacing the post in the blue area, or would it still require using get_post() regardless?
Forum: Fixing WordPress
In reply to: Comments form breaking designWorks perfectly. Thanks so much!
Forum: Fixing WordPress
In reply to: Comments form breaking designI my pages marked as private and forgot to make these two public before I posted. Try these codes
better
wrongAlso, with regards to the yellow page and the very long loading time, both will be attended to, but my site is not ready to be published yet, hence the reason I am on here. I currently have very large image files to be loaded on the current design, and the finished product will have an attractive error page with a center logo on darker blue.
- This reply was modified 7 years, 4 months ago by starwag.
Forum: Developing with WordPress
In reply to: Loop Showing 1 Post OnlyThanks! I think that is going to work. I just placed the one div over the php ending and it all started working beautifully. So simple, yet so complex. Thanks again!
Forum: Developing with WordPress
In reply to: Loop Showing 1 Post OnlyThanks! Yeah, in fact the whole site is showing the nested posts now (I’ll link it again). It’s on the part of the site right next to the scrollbar. It looks hidden because you have to scroll through that section’s scrollbar to see the other scrollable section inside of that, then that section has to be scrolled through to see the next scrollable section, and so on and so forth. Each scrollable section seems to display two posts, the first, and then the second which becomes its own scrollable section with two posts inside of it. Also, I upped the post limit to 10, just to see if I could get more posts than the 3 I was getting, which means there’s a lot more nested than there was before.