@Sparkum said:

Hmm so finally got infront of a computer, started from the bottom and worked my way up through the solutions and the most annoying thing is the problem more so appears to be my "content content content..." eh? Copied 5 paragraphs for Lerem Ipsum; turned height to auto and bam everything was perfect.
It didnt even attempt to format to the right when I copied the paragraphs in....
So thats really strange and annoying cause I was already adjusting height: auto; before making the post =/

Thanks for all your help guys! And hey, if you've got any suggestions for the website I'd love to hear them.

P.S. what are these developer tools you all speak of? The only website tool I've used is Firebug so I'd love to know of something else.

Thanks

EDIT: Literally didnt even need to height: auto; just added the paragraphs and bam, worked how I wanted it. I literally didnt even have a problem! Just the content I added somehow screwed it all up???

That's great!

Developer tools is like firebug but its on chrome, but its built in. Just hit F12. Firefox has tools built in also.

Sometimes the sites get funky from the nbsp;'s.

@MattSpeller said:

@johnhooks NoMachine may fit the bill nicely, thank you

No prob.

@MattSpeller said:

@johnhooks Ubuntu server - TV uses their own servers, you just put clients on anything you want to remote into

Ya that's the nice thing about them is it runs through the web port. Do you have a gui on your server?

I can understand how people can get lost though. There are so many bad tutorials and how to's out there.

For example, the gazillion tutorials that just tell you to turn off SELinux.

Ubuntu server or Ubuntu as a team viewer server? I haven't used team viewer on Ubuntu for a long time. I've switched over to NoMachine.

Welcome @Marc92!

@Reid-Cooper said:

Not familiar with Apper. What does it do?

It's like the Software Center on Ubuntu. You can still install through the terminal, just not use Apper to search by groups.

Has anyone got Apper working on Fedora 22 KDE yet? I still get the SearchGroups not supported by backend error and it's been like 7 months since someone reported it.

Does this stem from the What Are You Doing Right Now comments?

@WingCreative said:

@johnhooks said:

@WingCreative said:

@johnhooks said:

@WingCreative said:

Agreed that it's a combination of the inline styling and the non-breaking spaces used for the placeholder text. Oddly, the inline height was set to 120px when I checked it. Either way, setting "height: auto !important;" for the element will probably fix it as @johnhooks suggested.

The question is how the inline styling got there to begin with... I am assuming this is probably due to some javascript in the accordion plugin? Is there any setting in the accordion plugin that is set to about 120, or any settings related to height? If the !important flag works then it might not be worth bothering with for now, but generally every !important flag in your stylesheet is a shortcut that doesn't really address whatever root issue you're wrestling with.

I just unchecked the 121px in developer tools, it did initially show that way for me also. I used the !important just because it wouldn't override without it.

For whatever reason, sometimes these plugins have hard coded sizes (and in px even) so it's fun to have to do your own styling on top of their styling.

Same - I am hoping the inline styling is something that can be set in the plugin settings, but it's possible that it's just hard-coded in there. I thought it was odd that it was slightly different on my screen though, as if the inline style was being dynamically generated or something.

I'll admit I have plenty of !important flags in my own stylesheets due to things like this, I mostly mention it as a potentially more elegant way to solve the issue if OP is interested in learning more about CSS.

I edited the post but not in time :P. I wonder if it is dynamically changing based on resolution, but why a 1px difference? And why in px?

There's the mystery... without knowing which plugin is being used it's hard to know for sure.

If @Sparkum were interested in digging deeper into this, he could try pasting some dummy paragraphs from a Lorem Ipsum generator into one of the blank boxes before setting the height flag. It might be built to dynamically set the height for each accordion item, but I don't understand why the plugin dev would do that versus a simple "height: 100%" setting.

Ha I don't either. When I pasted the lorem ipsum content in, it didn't automatically resize, but that was through developer tools so it might do it correctly if you can refresh the page.

@JaredBusch said:

The current layout still sucks for replies. I see this in both chrome and iOS.

Notice that I typed the last sentence almost completely off screen.

I can't see what I'm typing in Chrome on Android until I start typing, then the text pops up above the keyboard, but until then I can't even scroll down.

@MattSpeller said:

@WingCreative said:

Hmmm... SAM can't post to Spiceworks?

Quick, everyone head over there and recommend SANs, FreeNAS and VMWare!

Pffft, I'm going to post about how epic RAID5 is with giant arrays - bigger the better.

Or how HA on VMware is a requirement for our business (and we didn't do any cost analysis).

@WingCreative said:

@johnhooks said:

@WingCreative said:

Agreed that it's a combination of the inline styling and the non-breaking spaces used for the placeholder text. Oddly, the inline height was set to 120px when I checked it. Either way, setting "height: auto !important;" for the element will probably fix it as @johnhooks suggested.

The question is how the inline styling got there to begin with... I am assuming this is probably due to some javascript in the accordion plugin? Is there any setting in the accordion plugin that is set to about 120, or any settings related to height? If the !important flag works then it might not be worth bothering with for now, but generally every !important flag in your stylesheet is a shortcut that doesn't really address whatever root issue you're wrestling with.

I just unchecked the 121px in developer tools, it did initially show that way for me also. I used the !important just because it wouldn't override without it.

For whatever reason, sometimes these plugins have hard coded sizes (and in px even) so it's fun to have to do your own styling on top of their styling.

Same - I am hoping the inline styling is something that can be set in the plugin settings, but it's possible that it's just hard-coded in there. I thought it was odd that it was slightly different on my screen though, as if the inline style was being dynamically generated or something.

I'll admit I have plenty of !important flags in my own stylesheets due to things like this, I mostly mention it as a potentially more elegant way to solve the issue if OP is interested in learning more about CSS.

I edited the post but not in time :P. I wonder if it is dynamically changing based on resolution, but why a 1px difference? And why in px?

@WingCreative said:

Agreed that it's a combination of the inline styling and the non-breaking spaces used for the placeholder text. Oddly, the inline height was set to 120px when I checked it. Either way, setting "height: auto !important;" for the element will probably fix it as @johnhooks suggested.

The question is how the inline styling got there to begin with... I am assuming this is probably due to some javascript in the accordion plugin? Is there any setting in the accordion plugin that is set to about 120, or any settings related to height? If the !important flag works then it might not be worth bothering with for now, but generally every !important flag in your stylesheet is a shortcut that doesn't really address whatever root issue you're wrestling with.

I just unchecked the 121px in developer tools, it did initially show that way for me also or are you saying that because it shows 121 in my screen?) If that's the case, maybe it's adjusting based on the resolution?. I used the !important just because it wouldn't override without it.

For whatever reason, sometimes these plugins have hard coded sizes (and in px even) so it's fun to have to do your own styling on top of their styling.

@Sparkum said:

Sorry faq should be live now:
And it is a faq plugin. Will give more details when not on mobile
Thanks

Oh I see now. I only saw the 404 also. So you have the accordions set up, you just want the content to fill the accordion.

It looks like the horizontal scrolling was from a bunch of non-breaking spaces (nbsp;). If you put in normally formatted text it looks ok. Just comment out the height of 121px and it should work.

Edit: It looks like that height is hard coded in the html. If you add this to your css file it should work:

.ui-accordion-content {
height: auto !important;
}

Since you're using WordPress I would just use an accordion plugin, that would be the easiest thing to do.

https://wordpress.org/plugins/tags/accordion

@MattSpeller I just told my wife this last night. It's funny how avatars change perception of things. Every post I read of yours comes out in a Ron Swanson voice in my head. I love it.

@MattSpeller said:

@johnhooks Oh good grief I thought you had all that installed on yours for a sec and I almost wept for your users lol

hahaha. I can't believe someone would use that for a directory server or mail server. I kind of want to see what would happen if you turn everything on.

@JaredBusch said:

@scottalanmiller said:

Yeah, but all of them in that general category do it too. None of them advise it, all of them allow it.

Not a single one I have seen takes it as far as Synology though.

Haha this is too far?

@scottalanmiller said:

Rather like people throwing every little workload onto a NAS. It isn't designed for that.

Ha like Synology putting web servers and DNS servers on their NAS units?