patv

since it’s not defined yet

It’s defined in functions/fe/setup.php

Why wouldn’t it be detecting it then?

It wouldn’t be a redefinition since it’s not defined yet – he can’t pull that value without getting a error. Thought if esmi’s code works, then use it. I’ve something new today myself ??

from @krishna’s like, seems like the password is encrypted using md5. check out this crypt generator

@agfreesafety, yes i probably caused more harm than good suggesting you to modify the PHP. Follow esmi’s instructions and create a child theme. I don’t know how to do this myself, but the advantage of creating a child theme is that if something breaks it has a fallback to its parent theme.

In your child theme, create a functions.php file and add the code I mentionned above.

What I know about using numeric values in permalinks is that it reduces the chances of clone permalinks to happen. What I’ve generally seen for wordpress blogs is the use of the date (such as the year and perhaps even month) followed by the postname, such as /%year%/%monthnum%/%postname%/, in order to avoid clone post permalinks should two posts have the same title.

Perhaps what you referring to aswell is the use of the post’s id instead of using the postname, such as /%post_id%/, where you have 0% chance of having two posts with the same permalink since IDs are always unique.

Either way, WordPress will increment the permalink if one’s already used so you never will have an error of two posts using the same permalink. Problem is that having your-post-permalink-2 isn’t the most beautiful name, because of the prefixed 2 at the end (if there’s two posts with the same permalink). That’s why including a temporal variable such as the year or month will reduce the chances that you’ll have two identical permalinks so they all remain as ‘organic’ as possible.

My point:
I’ve checked on my own sites. I use /%category%/%postname%/ for my posts. For my pages, the permalink structure is reduced to /%postname%/ because pages have no categories. So if you switch over to category/postnames, your pages permalinks won’t be affected, so your external links won’t be broken.

What’s the foreach() code? Can you post it?

@agfreesafety, the code i sent you is PHP, so it has to be set in the functions.php file. It won’t get recognized in a .css file.

Perhaps .sidebar-right is already defined in a parent CSS rule. Do you have access to firebug to check if there are any styling that would be hiding the sidebar when you rename the sidebar class to .home-right?

Depending how you’ve got your theme setup (is it a child theme or are you modifying the current theme?), then yes there may be some css rules that are defining the structure of your sidebar (through .sidebar-right). Best you don’t remove the existing ids and classes defined in the markup, but if you really want to defined a .home-right for the div, add it as a second class to the div:

<div class="home-left" ></div>
<div class="sidebar-right home-right"></div>

Ok. Given that your ‘static’ pages are already in WordPress (I was worried you were referring to static pages in that they were straight .html or .php files), changing the permalink structure won’t break those pages; they will simply have a different permalink.

if you want to structure your posts by category and them postname, then you structure would be /%category%/%postname%/ and this should give you simple postname permalinks for your pages, which may be what you already have for them.

The only problem you’d have is if you’ve posted links to your pages outside your site – they would consequently be broken if you change the permalink structure (which might change the permalink for your pages). In this case you can manually redefine the permailnks for your posts by going through each post editor.

Ok. This means that your static pages are listing under the Pages tab?

Can you post the HTML markup around a widget? I myself don’t know what the HTML structure surrounding a widget looks like, but if you post the markup, I’ll be able to write a CSS rule for you accordingly.

You might have to set the line within a function, such one that is triggered when WordPress is being loaded upon a page request. I can’t seem to find the action hook for you, but if you look around in the codex you probably will be able to find it.

When you’re talking about static pages, are you taking of pages in wordpress (static posts)?

First off, are you able to login onto your admin dashboard at all? if not:
What is the login error message that you’re getting? Is it an invalid username or password?

When you manually change the password in your cpanel, are you taking into account that passwords stored in the database are encrypted?