Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter kprensac

    (@kprensac)

    Hi Andrea,

    Thanks for the response. I tried that several times in every way and combination possible. It didn’t work. I don’t think that this is a path issue. I have a single external js file for each gallery that contains both the javascript for the API and also the javascript for the embedding and initialization of the flash object. Since the flash object is embedding and initializing just fine in every case, I don’t think that the domain mapping is creating any issue with finding that file. By the way, I’m not using any of the wp flash plugins either (kimili, etc.) but loading swfobject.js on each relevant page by way of functions.php. There doesn’t seem to be any problem with how that part of it is working either.

    Got nothing relevant from either hostgator support or the simpleviewer forum on this so I’m feeling pretty stumped at the moment. Any other comments or suggestions. Thanks again.

    James

    Thread Starter kprensac

    (@kprensac)

    OK Andrea — progress. That’s the info I needed and I changed those settings. There was one last piece of the puzzle. At hostgater subsite.com had to be changed from an addon domain to a parked domain. Once it was a parked domain, everything worked as expected.

    However, I seem to have lost functionality on some of the javascript controls on the gallery pages (it’s a photo gallery site using simpleviewer flash galleries). That’s a separate issue that I need to debug myself (unless you happen to have some idea offhand). At least the domain mapping issue is now solved. Thanks again for all your input.

    Thread Starter kprensac

    (@kprensac)

    Hi Andrea,

    Thank you very much for the response. Unfortunately, I’m not quite sure what you mean by “Change the folder links to the full domain.” I’ve gone to Super Admin -> Sites and found the site I wanted (in the case of my example it is listed as “/subsite/”). I then went to the edit page for that site. There are 4 fields that I see that I think would be relevant to your suggestion.

    In the top section “Site Info (wp_blogs)”, there are 2 relevant fields:

    1) Domain (currently listed as “main-site.com”); and
    2) Path (currently listed as “/subsite/”) with a checkbox underneath that says “Update siteurl and home as well.” – the checkbox is active

    In the next section “Site Options (wp_3_options)”, there are 2 other relevant fields:

    1) Siteurl (currently listed as “https://main-site.com/subsite/”); and
    2) Home (also currently listed as “https://main-site.com/subsite/”)

    I’m assuming that the “Domain” and “Path” stay constant but perhaps you can change the “Siteurl” and /or “Home” to the mapped domain of subsite.com. Am I even close to being on the right track? If so, I’ve tried several different combinations but can’t get it to work.

    I’m sorry for being thickheaded but I just can’t figure out what to do when you say “Change the folder links to the full domain.” Could you explain with a little more specificity and detail.

    I appreciate the information and effort.

    Thread Starter kprensac

    (@kprensac)

    Thanks for the reply. Yes. I built the theme COMPLETELY from scratch. I created the grid layout in CSS first and then added in all the functionality and styling, etc. Graphic design is not my strong point but functionality is exactly how I want it – and it’s all bilingual (which took a lot of work). In my first post above I also forgot to mention the the “Subscription” page is a highly customized frontend of PHPlist that I made to exactly match my WP theme. I wanted the site to be completely intergrated from a theme and UI perspective.

    kprensac

    (@kprensac)

    Thank you Kevin for the excellent solution. I agree with Dave that this should be part of the core build.

    This issue drove me crazy. It seems like it should be obvious. The answer, I think, is to edit /wp-includes/functions.php more or less between lines 1258 and 1275 (it is in a function called wp_die() )

    This issue drove me crazy. It seems like it should be obvious. The answer, I think, is to edit /wp-includes/functions.php more or less between lines 1258 and 1275 (it s in a function called wp_die() )

    This issue drove me crazy. It seems like it should be obvious. The answer, I think, is to edit /wp-includes/functions.php more or less between lines 1258 and 1275 (it s in a function called wp_die() )

Viewing 8 replies - 1 through 8 (of 8 total)