Thread

tsoares,

Juts to make sure we are on the right page. Everything worked on the dev subdomain but now trackbacks are not working for the production domain. The prodcution domain is a new site using MSM. You believe you have replicated everything.

http://blogs.cisco.com/ciscotalk/ is a site created using the multisite module.
ar is the blogname.

There is a one index.php under ciscotalk directory.

Have you any settings in the path.php file in the ciscotalk directory that need to be updated for the blogs.cisco.com subdomain?

Have you added the $site_name variable to the path.php?

EE Docs : Setup Domains and Sub-domains

Hi John,

Yes, Site_name was set up as ciscotalk in path.php

$site_name = "ciscotalk";

Pls tell me what else would you like me to check, this issue has been there from 2009/02, if you could give me more debugging tips quicker that would be appreciated.

Thanks.

Can you just comment it out with HTML tags, and not EE comment tags?  So we can see what is displaying in the source code?

=greg

Thanks Greg,

I added the html comments to the code and you could view the source of url to see the commented trackbacks code, but View source is not displaying EE tag :  {exp:trackback:url}

http://blogs.cisco.com/ciscotalk/ar/comments/together_we_lead—_2009_cisco_partner_summit/#comments

Pls let me know what are the next steps we can talk to resolve this issue.

Thanks again

To get to the bottom of this, can you try to a greatly reduced, minimal template? I’d also like to take the URL rewriting out of the equation for now, can you disable .htaccess for the time being? Are you still on build 20081212? If so I’d like to repeat my invitation to upgrade to the latest build, 20090515 as of today.

Thanks Ingmar,

I tried to with minimal template and also disabling of .htaccess code an both of them did not work. Would you say upgrading to current version will resolve the issue.

There are no guarantees, but it would help us to rule out corrupted files and make sure we are on the same page, code wise. I recommend it.

Thanks Ingmar,

I checked with the team and they are working on some enchancements. So It might take few weeks to upgrade to latest version.

Pls tell me if any thing else I could check to fix this issue,before upgrade.

I am afraid troubleshooting is rather difficult if we can’t rule out a corrupted file.  When you say the team was “working on some enhancements”, do you mean to the site itself, or to EE’s code? Let us know how it goes. If it takes a while, that’s not a problem: we’ll be here and ready when you are.