• 0

PHP includes with sub folders... how?!


Question

Hey.

Im trying to change my site to use subfolders. At the moment i have all the pages, CSS and a header.php in the root. Now i have:

header.php

footer.php

index.php

css.css

products/page1.php

products/page2.php

products/page3.php

etc

The include works from index.php, but not from page1.php I understand that this is because from page2 its looking for the header.php in the products/ folder, but i dont know how to fix it. Ive tried

<?php include ('../header.php'); ?>

And that didnt work.

Any ideas would be greatly appreciated.

Link to comment
https://www.neowin.net/forum/topic/626575-php-includes-with-sub-folders-how/
Share on other sites

8 answers to this question

Recommended Posts

  • 0

is the header included in the product pages? (page1.php, page2.php, page3.php etc) ?

I assume the product pages are included in index.php and the problem your having is that it cant find the header file from the product page because its looking in the wrong place, is that right? :p

I think what you need to do is take the header includes out of your pages and just put use one include header statement at the top of index.php, that way you only have one statement and its looking in the right place for it.

  • 0

Try ./ because that looks for the root folder.

If I understand you correctly your going from

products / page#.php

to

header.php in root.

If thats the case, do ./header.php and it should go to the root folder and then find header and it should.

if your going from

root

to

products/page#.php

Then do include("products/page#.php")

This is all rough but it should work.

I hope I understood you right.

Cheers.

  • 0

assuming your webhost allows you to use .htaccess to set php settings, set an includes directory. for example here's mine.

php_value include_path ".:/users/m/marc2003/includes"

i now place any common php files inside this folder. now i can call on the file simply using

include 'header.php';

folder structure is now irrelevant as php will check in my includes folder first.

  • 0
  Sikh said:
Try ./ because that looks for the root folder.

afaik, ./ is only a reference to the current working directory, it is not a link to your webroot. in this case, you may be correct, but if the script that was running is actually in mydomain.ext/some_folder/ rather than just in mydomain.ext/, then ./ would refer to the subfolder, not the root folder.

  • 0

I usually get around this by including a variable somewhere higher up that defaults to "./" and use that when trying to do my includes. Change it to manually perhaps if your in a sub directory.

Probably not best way.. you could use $_SERVER["DOCUMENT_ROOT"] I think which will get you the path directly to header.php if your in a sub folder.

  • 0
  marc2003 said:
assuming your webhost allows you to use .htaccess to set php settings, set an includes directory. for example here's mine.

php_value include_path ".:/users/m/marc2003/includes"

i now place any common php files inside this folder. now i can call on the file simply using

include 'header.php';

folder structure is now irrelevant as php will check in my includes folder first.

<?php

// Works as of PHP 4.3.0

set_include_path('/inc');

// Works in all PHP versions

ini_set('include_path', '/inc');

?>

  • 0

How rude of me, i completely forgot i made this thread!

Well, thanks for all the responses. Ive managed to fix it now, but ill give a nice detailed explanation of what i wanted and how i fixed it for the benefit of others.

Basically, I was trying to include my header (which is in my root directory) from a page in a sub directory.

I was able to call the header itself with

&lt;?php include ('../header.php'); ?&gt;

- but my problem was, the header contained my nav bar and my css <a href ="style.css">

By doing it this way, page in the subfolder was looking for the style.css in the subfolder directory, not in the root where it was with the header.

So, not only did i need to put

&lt;?php include ('../header.php'); ?&gt;

in each of the pages in the sub folders, i also needed to change my reference to the css to

href="/style.css"

- see the "/"

Finally, the reason i didnt use $_SERVER["DOCUMENT_ROOT"] is because im doing the development in a XAMPP test server on my pc - with my files not in the root. So i thought it would all screw up once i uploaded to my webserver. Plus, because im only going to need to go down to one sub folder, the "../" is a good enough solution for me.

Thanks for all the replies though - good to know theres a decent community here.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft reportedly planning to lay off thousands of employees, mostly in sales by Usama Jawad Back in May 2025, Microsoft decided to lay off 3% of its workforce, which amounted to roughly 6,000 employees. It claimed that this decision allowed it to implement better organizational changes in a "dynamic marketplace". Now, a new report claims that the Redmond tech firm is planning to lay off thousands more next month. Citing unnamed sources, Bloomberg reports that as the company continues investing heavily in its AI ventures, it is about to announce layoffs of thousands of workers as early as next month. This reduction in workforce will primarily affect sales teams, but they won't be the only ones affected. That said, the sources did mention that the timing for this announcement may change. This move, if true, won't be entirely surprising. In April 2025, Microsoft announced that it will be relying more on third-party firms to sell its software to small- and medium-sized customers. It's currently unclear how many employees will be impacted by this change, but even if the layoff percentage is in the single digits, it would still be significant as it would be impacting the professional careers of thousands. The May 2025 layoffs primarily impacted engineering and product teams. The other major round of layoffs prior to this was the decision to eliminate 10,000 jobs back in January 2023. Those represented 5% of the total workforce at that time, with numerous teams, including the one leading Mixed Reality (MR) efforts, being heavily impacted. It is interesting to note that if the timing of the announcement for layoffs is accurate, it would be soon after Microsoft closes its fiscal year at the end of June 2025. Although we'll get financial reports for the latest quarter soon after too, one has to wonder what the human cost of profit is, as Microsoft continues to report billions of dollars in revenue every quarter. Source: Bloomberg (paywall)
    • Ah .. lockout for suspicious activity. I bet they uploaded the SanDisk utility detected as malware
    • Microsoft 365 will soon disable outdated authentication protocols for file access by Usama Jawad On a fairly regular basis, Microsoft disables outdated protocols that are used to access its services. In the past few years, the company has deprecated Basic Auth in Exchange Online and cut access to Outlook for third-party apps relying on this protocol. Now, it has decided to get rid of old authentication protocols for file access across Microsoft 365 services. As reported by Bleeping Computer, Microsoft has posted a message on its Microsoft 365 Admin Center. Starting from mid-July 2025, the company will begin disabling legacy authentication protocols used to access files across Microsoft 365 and Office apps, SharePoint, and OneDrive. Essentially, applications or services which use the Relying Party Suite (RPS) or FrontPage Remote Procedure Call (FPRPC) will to perform browser-based authentication to perform open operations on Office files will no longer be able to do so. As expected, this is primarily being done to improve the cybersecurity posture of various services. Microsoft states that RPS can be brute-forced and phished with relative ease as it is fairly outdated. Similarly, FPRPC is typically used for remote web page authoring and it is susceptible to exploitation through various vulnerabilities too. As such, both of these protocols will be disabled by default starting from mid-July 2025, with the rollout of this change targeting completion by August 2025. The Redmond tech giant will update the protocol baseline by default without mandating any licensing changes for customers. In addition, once these modifications are rolled out, Microsoft 365 will require admin consent to get third-party access to files and sites. IT admins can view the guidance available here to configure admin consent workflows. Microsoft says that these changes align with the principles of its Secure Future Initiative (SFI). Earlier today, it announced the rollout of improved security defaults for Windows 365 citing the same reasons too.
    • This is how you kill your own business.
  • Recent Achievements

    • First Post
      Fuzz_c earned a badge
      First Post
    • First Post
      TIGOSS earned a badge
      First Post
    • Week One Done
      slackerzz earned a badge
      Week One Done
    • Week One Done
      vivetool earned a badge
      Week One Done
    • Reacting Well
      pnajbar earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      705
    2. 2
      ATLien_0
      283
    3. 3
      Michael Scrip
      217
    4. 4
      +FloatingFatMan
      195
    5. 5
      Steven P.
      130
  • Tell a friend

    Love Neowin? Tell a friend!