Hm… eeSiteKit 1.x wasn’t built to run in EE 2.0x. Glad to hear most of it works though. There was enough bugs in past versions of EE 2.0-betas that the kit didn’t do well, so we quit testing it. Now that EE has most of those resolved with this January build/version, things might do much better than months ago.

It’s most likely a vocabulary issue in some of the conditionals that help create the navigation. EE tries to update stuff in the templates when you run their upgrade script, but we can’t expect it to catch everything.

Rather than put you though 50 posts here, could you send me SuperAdmin access to the site in question. Please send the password in a separate communication than the username and path to the Control Panel. You can use the PM system here in the board if you like.

I’ve got 2 sites launching tomorrow and am on a third project with a Monday deadline, so I’ll do my best to get to your site today, but it could take a little longer.

Thanks, Kurt.

But, before I send you off on a wild goose chase, I would like to do a little more poking around on my own. I need access to the previous User Guide, though, if that’s possible. I will post any progress here.

Sorry, we took the old guide down, I can pull out a chunk or two though, as I still have it here in the database, but I don’t have the sever configured to allow traffic to the old docs (seperate MSM site) at the moment.

If the main nav is just missing content, then look in the core/.nav_main_engine template. That’s where the magic happens.

Maybe you could send me the code you have in there now, and I might be able to spot what’s up.

Here’s an update:

After our EE 1.6.8 install was successfully upgraded to EE 2.0 PB (not an easy task, btw), we then wanted to verify functionality of one of our sites running under MSM that was based on eeSiteKit 1.

Everything seemed to be working as expected with the exception of navigation.

The problem was caused by failure of the EE 2.0 installer to consistently replace “embed:weblog” and “{weblog}” with “embed:channel” and “{channel}, respectively.

After carefully using EE CP Search and Replace operations on the eeSiteKit templates, everything is back to normal with eeSiteKit as far as we can see.

+

Next, we are anxious to try eeSiteKit 2 in EE 2.0, but have read eslewhere in these forums that there are “significant” issues in EE 2.0 and eeSiteKit code rewrites that presently aren’t allowing that to happen.

Glad to hear its working for you.

I am working on a version of eeSiteKit for EE 2.0, but we’re at least a few weeks (perhaps a month or 2) away from that being ready. I am working on it every chance I get but have been very busy with running NetRaising lately and that’s slowed development of eeSiteKit a tad bit.

Appreciate the update!