Jump to content

WPCDN

Retired Forum Member
  • Posts

    8
  • Joined

  • Last visited

About WPCDN

WPCDN's Achievements

Junior Member

Junior Member (1/3)

0

Reputation

  1. Hi, Our post above is somewhat of a step-by-step. There are other step-by-step posts in these forms and elsewhere on the web. The basic concepts are fairly easy, but sometimes it takes trial and error to get them to start working. Then it flows pretty easily. Good luck! Mark
  2. Retry: Strategerizer, Thanks for the kind words. Sure. I'm not sure how much you've tried yet, so please forgive me if I touch on things you already know. In summary, we used the method of copying and pasting our site design (page source code) into the following WHMCS template files: header.tpl - basically contains everything up to your main page content homepage.tpl - contains the main page content footer.tpl - contains everything after the main page content (including, in our case, the right column) This method is essentially the same whether you're using WordPress, Joomla!, any other CMS, or just plain HTML. But here's how we did it in conjunction with WP: We created a WordPress page (that appears in the main menu) called "Support". In this WP page, we added all the content we want our main support portal to have. This page actually does not appear in the final site, but serves as a master for our integration. In the early stages of our integration, we named our WHMCS folder something other than "support". This way, when we went to the "Support" menu item, we could access the WP page we created. We copied the source code of the WP page, then renamed our WHMCS folder to "support". This makes the WHMCS system appear (instead of the WP page) when you click the "Support" menu link. WP will defer to a directory if there is one with the same name as a page. We pasted the appropriate bits of code into the template files. Note that you may need to experiment and pay careful attention to closing <div> tags, etc. Be sure to clear the templates_c folder after uploading any changed files. Also note that you can easily edit the .tpl files by changing their extension for editing, then changing it back before uploading. Or you can use a program that edits them directly, for example we used gedit in Linux. The SSL "mixed content" issue turned out to be an absolute link to our page background that one of our designers added during our CDN testing. That caused the background to be loaded as an http item instead of https. After we restored the original relative link, the issue went away. The Station from WooThemes. The procedure would be the same, but you'd need to view the source of a page generated with the different theme, then copy and paste the appropriate parts into the template files. Of course, you can create multiple WHMCS templates by copying and renaming a template folder. So, if you change themes but want to keep the possibility of returning to the old one, create a new WHMCS template for each WP theme. I hope this points you in the right direction. Please don't hesitate to ask for any additional information. Best regards, Mark
  3. Excellent integration, looks completely unified with the rest of the site.
  4. Fixed. I think this might be a cosmetic issue in the Web 2.0 cart? We didn't change any headers or anything that should have made "Shopping Cart" appear twice. We ended up removing that header entirely from the main cart template file, and the duplication went away. I think we've found the issue and fixed it. Testing continues... Thanks again to everyone for your feedback.
  5. Hi All, Please let us know what you think of our WHMCS integration: http://www.wpcdn.com/ The "Support" tab in the main menu is WHMCS. Any suggestions are appreciated. Best regards, Mark WPCDN - WordPress Content Delivery Network http://www.wpcdn.com/
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated