Skip to content

Commit 5aecc72

Browse files
committed
add include paths note
1 parent d16e238 commit 5aecc72

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

en/mapfile/include.txt

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,11 @@ Notes
3535

3636
- File location can be given as a full path to the file, or (in MapServer >=
3737
4.10.1) as a path relative to the mapfile.
38+
39+
.. note::
40+
41+
Nested :ref:`INCLUDE` statements (such as an INCLUDE within an INCLUDE)
42+
must be relative to the top-level mapfile, not its parent mapfile.
3843

3944
- Debugging can be problematic because:
4045

en/mapfile/index.txt

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@
1111
:Contact: steve.lime at dnr.state.mn.us
1212
:Author: Jeff McKenna
1313
:Contact: jmckenna at gatewaygeomatics.com
14-
:Last Updated: 2022-08-29
14+
:Last Updated: 2025-06-04
1515

1616
The Mapfile is the heart of MapServer. It defines the relationships
1717
between objects, points MapServer to where data are located and
@@ -122,6 +122,11 @@ Notes
122122
* File paths may be given as absolute paths, or as paths relative to
123123
the location of the mapfile. In addition, data files may be
124124
specified relative to the SHAPEPATH.
125+
126+
.. note::
127+
128+
Nested :ref:`INCLUDE` statements (such as an INCLUDE within an INCLUDE)
129+
must be relative to the top-level mapfile, not its parent mapfile.
125130

126131
* The mapfile has a hierarchical structure, with the MAP object being
127132
the "root". All other objects fall under this one.

0 commit comments

Comments
 (0)