Solved - Empty Modular Page

Support
, ,
1

I created a Modular Page as Home Page, but the Frontend page stays empty. No elements are created in the HTML section. I created and tried every page type and every one works, except the modular pages.

Frontend and page overview in admin panel
Frontend and page overview in admin panel4400Ă—1098 127 KB

Frontend and page overview in admin panel

Theme is Typhoon. Following Plugins are installed:

  • Admin Panel v1.10.43
  • Color Tools v1.1.1
  • Email v4.0.4
  • Error v1.8.0
  • Flex Objects v1.3.6
  • Form v7.2.1
  • License Manager v1.0.2
  • Lightbox Gallery Premium v1.0.6
  • Login v3.7.6
  • Markdown Notices v1.1.0
  • Problems v2.1.1
  • Quick Tray Links v1.1.1
  • Shortcode Core v5.1.3
  • SVG Icons Premium v2.5.0
2

@nido, When having issues with pages it’s usually a good habit to share the header/frontmatter of the page. I guess that’s where the root of the problem lies.

Please read the docs on:

Also please consider not using images of folders, code, frontmatter, etc. Images are often hard to read, especially for the visually impaired and/or people using screen readers. Also, images of code snippets cannot be copy/pasted.

1 Like
3

Thx for your correction on my request. From what I read on the article on modular pages, the modules should appear as folders on the webserver. My folder structure looks as follows:

pages
  01.start
    _header
    _introduction
    _some-text
    _contact
  02.news
    hello-world

The modular.md file of the modular page “start” should contain various information on its modules. But it doesn’t. This is the whole content of the file:

---
title: Start
---

Can the file be regenerated? Or can I fix it manually by copying the code example from the wiki page and renaming the modules?

4

@nido, the collection of a modular does not get generated magically by Admin… You’ll have to define it yourself using a file editor (eg. vscode) or in “Expert” mode of Admin.

5

Thank you for your help :slight_smile:
I didn’t think, that I had to add module collection on the parent module page, since I think it could be pulled from there…
But I added it and now it works.