Errors with Design Extender

I've recently updated my copy of Design Extender and am using the Power CMS Builder portion of the plugin. When I first uploaded all the info, integrated the database and updated my connection file, I was getting an error:
Fatal error: Call to undefined function virtual() in /homepages/43/d259262383/htdocs/SynikFC/gallery.php on line 1

Replacing virtual' with 'include_once' took care of this (and another on line 5), but now I'm getting this fatal error;
Fatal error: Call to undefined function WA_getCMSContent() in /homepages/43/d259262383/htdocs/SynikFC/index.php on line 23

Just wondering if I'm missing a step... I never had these issues before when using the Power CMS Builder or an older version of the Design Extender extensions.

UPDATE:
After some testing I changed the 'include_once' to just 'include', and then removed some of the file path as there was some local info still on the lines and we're all good. You'd think I'd know better after using the software for a few years off and on...

Chalk up another one to PEBKAC

This is a Dreamweaver issue.

When defining your site, There is an Option is the Site definition settings:

"Create Links Relative To"

using the Site option causes DW to use the virtual() function for included files. This function is only defined on some PH server, and even when it is defined, it writes a bit to the page header that causes the header already sent error on redirects.

instead use the Document settings so that DW will use the require_once() function for including php files. the require_once() function does not include the issues that virtual() does.

Thanks for the reply, I updated my first post with my findings while you were responding :) My issue was the path in the include that was still set to my local file structure.

You wouldn't have the issue at all if you set the site definition to use Document paths instead of Site relative paths.

The underlying cause of the problem is the Crate paths relative top setting.

Yes, once the problem exists, the code needs to be edited and the paths changed, but to prevent the problem in the future, change the way the site is set to create paths.

Roger that :) Thanks again for the quick replies. It's been a while since I used Dreamweaver so hopefully some of these simple things come back.