dannyka

I’m another who’s now quite happy with 1&1. It took awhile to get used to the way they do things and have things laid out, but it all seems to be there. WordPress was actually the easiest blog system to install on 1&1 — of course, that may be because it was the last blog I installed. ??

D’oh! What a dork I am.

I was looking around the WordPress Codex to learn just what it can do, and what do I find??? A couple of paragraphs on ‘The difference between a blog and a CMS”.

Live and learn.

–Dan

Applied the fix. Everything looks great!

–Dan

Thanks for the replies. For my purposes I decided to go with a blog and add on what I need. I now have a basic WP installation going on my friend’s server. That was quite the experience! He has IIS and it didn’t quite work ‘out of the box’. Thanks to some very helpful people like yourselves, I was able to get it working.

NuclearMoose — I put basically the same search into Google before I posted here. The answers mostly had to do with ‘using a cms/weblog, what’s the diff between this and that’, or something to that effect. Not really the answers I was looking for. I clicked on your Google link today and guess what? This thread is #2! LOL!

–Dan

John,

I’m not getting those messages so I’m afraid I’m not going to be of much help. Hopefully someone else with a bit more php and/or IIS experience can lend a hand here. Good luck!

–Dan

Wow! Thanks for all the help.

I haven’t tried Kevin‘s solution, but I did implement agw‘s and now everything seems to work fine.

John, be sure to change the include line in edit.php back to “include (ABSPATH . ‘/wp-blog-header.php’);”.

That should do it. Again, thanks for all your help!

–Dan

Oh, sorry. I should’ve mentioned in the post above that the “include…” line is in edit.php. Just do a search for wp-blog-header.php.

–Dan

Here’s the latest.

I tracked it down to the line “include(ABSPATH . ‘wp-blog-header.php’);”. For some reason, IIS (I’m assuming) is having a problem with that line. I played around with it a little and finally changed it to “include(‘./wp-blog-header.php’);” This has allowed it to bring up the posts menu.

The only thing now is that on the Posts tab it tells me ‘No Posts Found’. I’m assuming it should show at least one even if I’ve never put anything in. I guess tomorrow I’ll debug it some more…

–Dan

Well, here’s what I’ve found so far.

I edited a file called menu.php. That seems to have the menus that control what you select. It includes ‘post’, ‘link-manager’, etc., in addition to ‘edit’. I noticed that if you try going directly to a page, it will take you there. Try logging in, then type https://www.[yourdomain.com]/wp-admin/page-new.php. That will take you directly to the Write Page. You’ll notice that the main menu is on top (starts out “Dashboard Write Manage…”). “Write” is highlighted and under that are the tabs “Write Post” and “Write Page” and you are on “Write Page”. Now, if you enter one that is under ‘control’ of edit.php, try categories.php, you’ll see that the main menu is still there, but there is no sub-menu. You are on the Categories page, but it just doesn’t look correct. I’m assuming you should have an Edit Submenu with all the options listed.

So my question is: Why is that? Why doesn’t the Edit menu come up? Will someone with a little more WP & PHP knowledge help a poor noob out here? Pretty-please-with-sugar-on-it?

I’m going to try playing with menu.php and see if I can get it to bring edit up. I’m not sure what else to do. It might have something to do with IIS & variables, but who knows.

I’ll keep you posted. Thanks for letting me know I’m not the only one out there. ??

–Dan