Include Page Warning: “Outside Site Definition” Triggered by Navbar Component?

[pilotdave]

I’m working on a PHP project in Wappler (v6.8) and encountering a persistent issue when using include files — specifically when including a Bootstrap 5 navbar inside a header.php file.

When I open header.php, which starts with the standard Wappler include comment (referencing index.php as the head-page), I consistently receive this warning:

“Your page is located outside a Site defined in the Site Manager. Some of the visual elements might not work properly.”

This happens even though:

• The file is in the correct project root

• I’m opening both index.php and header.php via the Pages panel

• The head-page file exists and is correctly referenced

• The project works correctly in the browser and everything functions as expected

I replaced the navbar inside header.php with a simple text container — and the warning disappears. That leads me to believe the Bootstrap 5 navbar structure (possibly the collapse toggler, data attributes, or nested elements) is what’s triggering the problem with Wappler’s design parser.

I have tried the following to no avail:

• Adjusting the head-page reference (relative path, root slash, etc)

• Restarting Wappler and reopening the project

• Testing in a clean project

• Rebuilding the navbar manually vs using the visual builder

Has anyone else experienced this when using navbars or other dynamic Bootstrap components inside PHP include files? Is there a known workaround or an update to the recommended practice for includes in PHP projects using Wappler?

I am just learning Wappler and this could be a showstopper for me.

[Teodor]

Please post your include code here.

[pilotdave]

[pilotdave]

[pilotdave]

Interestingly the page has lost its CSS formatting.

[Teodor]

When you run your page in the browser do you see errors in the dev tools/console? Also, how are your links set up in the project options - relative to document or relative to root?

[pilotdave]

No errors at all shown in the dev console. Set up to document.

[Teodor]

And the page renders good in the browser? all the styles there etc?

[pilotdave]

Yup.

I have created a new site and made the links relative to site root and exactly the same thing occurs.

[Teodor]

How is your project set up? what server are you using? Where do you store the files?

[pilotdave]

I have local files stored on my Mac and the server is a linux server with PHP & MySQL hosted by IONOS.

[pilotdave]

[pilotdave]

[Teodor]

@pilotdave

Your links are relative to site root in the settings

But your actual links on the page are document relative?

@pilotdave

Have you changed this setting back and forth? Try resaving the pages please. Also try opening the header include and select the main page again in app structure panel then resave it.

[pilotdave]

I did change the site root/document setting. Have resaved them all and it is still happening. As I said I even set up a new site and it happens. Happens on both of my Macs as well.

[pilotdave]

[Teodor]

I just tested this and cannot recreate the problem.
When you change the links relative to site root and save the main page, its header links are automatically changed from document relative:

<script src="dmxAppConnect/dmxAppConnect.js"></script>

to root relative

<script src="/dmxAppConnect/dmxAppConnect.js"></script>

Also re-selecting the head page in the include changes the link to it from:

head-page="index.php" 

to

head-page="/index.php" 

Something is probably not correct or corrupted in your site config or Wappler config. Try restarting and/or reinstalling Wappler.

[pilotdave1]

Had to set up a new account as the forum wouldn’t let me post anymore today.

OK, I have uninstalled Wappler, reinstalled. Set up a new site and it still doesn't work properly.

Thought I would try it on my Shadow PC (virtual) and with the old site it all works perfectly. So it would seem to me that this is a Mac only issue as it happens on both of my Macs but not my virtual windows PC.