What kind of "includes" does sitecake support?

#1

What kind of “includes” does sitecake support? For example, can the includes described at the following link work? http://www.w3schools.com/howto/howto_html_include.asp

When I use them I am only able to edit the index.html file. If I go into edit mode and click a menu item the corresponding page appears, however, it is no longer in edit mode. I am using the includes for headers, menus and footers.

#2

Hi, rendering of edit mode links is done on server side and includes you are trying to use are done on client side. Taking an example from your link, you could do something like this (I used jQuery, but also can be easily done without jQuery)

index.html

<!DOCTYPE html>
<html>
<script src="http://www.w3schools.com/lib/w3data.js"></script>
<script src="https://code.jquery.com/jquery-3.1.1.min.js" integrity="sha256-hVVnYaiADRTO2PzUGmuLJr8BLUSjGIZsDYGmIJLv2b8=" crossorigin="anonymous"></script>
<body>

<div id="main-nav" w3-include-html="content.html"></div> 

   <script type="text/javascript">
        $(function() {
            if ( window.sitecakeGlobals && sitecakeGlobals.editMode ) {
                $('#main-nav').attr('w3-include-html', 'sitecake.php?scpage=content.html');
            }
            w3IncludeHTML();
        });
    </script>

</body>
</html>

content.html

<ul class="sc-nav">
    <li><a class="active" href="./" title="Home">Home</a></li>
    <li><a class="" href="/about.html" title="About">About</a></li>
    <li><a class="" href="/portfolio.html" title="Showcase">Showcase</a></li>
    <li><a class="" href="/contact.html" title="Contact">Contact</a></li>
</ul>

URLs in menu links should be existing pages if you are using 2.3.7dev

#3

I have made the changes you describe and it now works as follows, when the user:

  1. logs in by clicking Login button at index.html
  2. clicks another page name from the navigation pull-down menu
  3. edits page content and clicks outside of element
  4. clicks Publish button (changes are saved to server - thank you).
    However, when user then goes to any other page, he is no longer in edit mode. To return to edit mode he must go back to index.html, login again, and then repeat the above steps. Is that the way it is supposed to work? My users can work with this flow of always having to return to the index.html page to make more edits, if it is necessary.
#4

You would need js code from index.html on every page where you include content.html