Title: NitrousCloud's Replies | WordPress.org --- # NitrousCloud [ ](https://wordpress.org/support/users/nitrouscloud/) * [Profile](https://wordpress.org/support/users/nitrouscloud/) * [Topics Started](https://wordpress.org/support/users/nitrouscloud/topics/) * [Replies Created](https://wordpress.org/support/users/nitrouscloud/replies/) * [Reviews Written](https://wordpress.org/support/users/nitrouscloud/reviews/) * [Topics Replied To](https://wordpress.org/support/users/nitrouscloud/replied-to/) * [Engagements](https://wordpress.org/support/users/nitrouscloud/engagements/) * [Favorites](https://wordpress.org/support/users/nitrouscloud/favorites/) Search replies: ## Forum Replies Created Viewing 5 replies - 1 through 5 (of 5 total) * Forum: [Your WordPress](https://wordpress.org/support/forum/your-wordpress/) In reply to: [Please critique my site :)](https://wordpress.org/support/topic/please-critique-my-site-2/) * [NitrousCloud](https://wordpress.org/support/users/nitrouscloud/) * (@nitrouscloud) * [14 years, 10 months ago](https://wordpress.org/support/topic/please-critique-my-site-2/#post-2168538) * Hello Vince, * Regarding the floating sidebar, here is what you have: * ``` #sidebar { margin: 0; #sidebar{position:fixed; top:10px; right:10px; width:230px;} } ``` * but if should just be: * ``` #sidebar { margin: 0; position:fixed; top:10px; right:10px; width:230px; } ``` * See how that works? * Basically, HTML is made up of elements, and those elements use CSS to manipulate them. Elements have various defaults – for instance, an `` element (for images) stays inline with the text. But `
` doesn’t stay inline, it occupies an entire section for itself. * Each element can be labeled with what is called an `ID` or a `CLASS`. ID’s can only be used once, CLASS can be used an unlimited amount of times. So, imagine you have one header, you might use an ID (`ID="header"`). But you may have a ton of buttons, so you could use a CLASS on everyone over and over (like `CLASS ="button"`). * To reference elements in the css, you use a period (“.”) for CLASSes, and a hash sign (“#”) for IDs. * The example of the sidebar, `#sidebar` means we are referencing and element with an ID labeled `sidebar`. We then wrap everything we apply using the CSS in curly brackets, like this `{ my css goes here }`. * Each CSS effect follows this structure: `Name Of Style: Style parameter;`. The use of the colon and semi colon is really important. * So, in summary, it looks like `class or id (. or #)NameOfElement{style:styleParameter;}` * Do you see why the edit didn’t work? * Now, if you use the code I provided, the sidebar will go up into the top right corner and stay there. However, you sidebar is taller then most screens are, which means people won’t be able to see the bottom of the sidebar. You may want to just move a single element into the corner. You can easily move single elements( like your cloud tag) or the entire thing, but picking and choosing what you want to move may get tricky (you have to get your hands dirty and do some coding!). * Finally, regarding the infinite scroll, I haven’t actually used the plugin, so I can’t say for sure, though I could see where WP-paginate and WP-Page numbers may conflict. I’d have to look at your actual side to tell for sure. * Forum: [Your WordPress](https://wordpress.org/support/forum/your-wordpress/) In reply to: [Please critique my site :)](https://wordpress.org/support/topic/please-critique-my-site-2/) * [NitrousCloud](https://wordpress.org/support/users/nitrouscloud/) * (@nitrouscloud) * [14 years, 10 months ago](https://wordpress.org/support/topic/please-critique-my-site-2/#post-2168459) * You’re site looks pleasant – nice job! Especially for a beginner. * As for infinite scrolling, [take a look at this plugin](http://wordpress.org/extend/plugins/infinite-scroll/). * And regarding a floating side bar, do you just mean a side bar that is always on the page, as you scroll down? That is fairly simple with CSS: * `#sidebar{position:fixed; top:10px; right:10px; width:230px;}` * Just put that into your style.css file – looks like `#sidebar` is around line 312. * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [301 Redirects: Will WP automatically do this](https://wordpress.org/support/topic/301-redirects-will-wp-automatically-do-this/) * [NitrousCloud](https://wordpress.org/support/users/nitrouscloud/) * (@nitrouscloud) * [14 years, 10 months ago](https://wordpress.org/support/topic/301-redirects-will-wp-automatically-do-this/#post-2171317) * In the background, WordPress uses a numerical structure for your posts and pages, so that when you change your permalinks, it can properly route to the new URL. * So you shouldn’t have any problems! Note that you _may_ have problems if you change it in the future (meaning it’s ok to change from default to something else, but changing it around afterward [may lead to complications](http://wordpress.org/support/topic/what-happens-if-you-change-permalink-structure-multiple-times?replies=9)). Best thing to do is just try it – you can always revert back to the default structure. * Same question asked: [Is it too late for Permalinks?](http://wordpress.org/support/topic/is-it-too-late-for-permalinks?replies=4) * Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) In reply to: [Category Redirection and 404 Problem](https://wordpress.org/support/topic/category-redirection-and-404-problem/) * [NitrousCloud](https://wordpress.org/support/users/nitrouscloud/) * (@nitrouscloud) * [14 years, 10 months ago](https://wordpress.org/support/topic/category-redirection-and-404-problem/#post-2165098) * Quoting from the [codex: using permalinks:](http://codex.wordpress.org/Using_Permalinks) * > For performance reasons, it is not a good idea to start your permalink structure > with the **category**, tag, author, or postname fields. The reason is that > these are text fields, and using them at the beginning of your permalink structure > it takes more time for WordPress to distinguish your Post URLs from Page URLs( > which always use the text “page slug” as the URL), and to compensate, WordPress > stores a lot of extra information in its database (so much that sites with > lots of Pages have experienced difficulties). So, it is best for the first > structure tag to be a numeric one, such as /%year%/%postname%/. * Perhaps the problem you are experiencing is due to starting with a non-numeric permalink. * Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/) In reply to: [My site says "This site is still under development".](https://wordpress.org/support/topic/my-site-says-this-site-is-still-under-development/) * [NitrousCloud](https://wordpress.org/support/users/nitrouscloud/) * (@nitrouscloud) * [14 years, 10 months ago](https://wordpress.org/support/topic/my-site-says-this-site-is-still-under-development/#post-2169260) * It appears you have a bigger problem at hand. * You have an embedded iFrame: * `` * You’ve either been hacked, or have a malicious plugin/theme. Viewing 5 replies - 1 through 5 (of 5 total)