Recently Browsing 0 members
No registered users viewing this page.
This is a textformatter module that will automatically replace titles of other pages on your site with links to those pages. For example, if you have a template glossary-term, and mention the exact title of one page using that template in a textfield, the title will be automatically linked to that page (if the textfield uses that formatter). This is good for SEO, and saves you some manual labour. You can configure which templates should get automatically linked, and of course the formatter is only active for the fields you add this formatter to. Note that if you need more manual control over when and where titles are automatically linked, you're probably better of using Autolink from a Glossary by @mr-fan.
Allows you to limit the automatic links by template. Only includes published & visible pages by default, with an option to include hidden pages. Automatically excludes the current page, with an option to change that behaviour. Doesn't overwrite existing links, and detects most edge cases (titles inside other tag's attributes, titles inside existing links et c.). Supports multi-language sites. Titles will only be linked if a title in the current language is set. Can add configurable attributes to all automatically created links. Includes the ability to use page fields as replacement patterns for attributes. For example, you can create CSS classes that include the name of the template of the linked page. Queries the database directly for improved performance. Only queries the database once per request & language. Download & Documentation
The module is now available in the modules directory: https://modules.processwire.com/modules/textformatter-page-title-links/
You can download & install it through the backend using the classname TextformatterPageTitleLinks.
To install it manually, download or clone the module from the Github repository into your site/modules folder and install through the backend.
The complete documentation can be found in the README in the repository. Make sure to check out the module configuration page after installing the module.
PHP 7.1 or higher ProcessWire 3+ (it will probably work in older versions, I haven't tested those though). This is my first module, I hope it may become useful to some of you 🙂
If you find any errors or have some other suggestions or feedback, let me know!
I'm a new to website building. Learned some CRASH course of js,jquery,php. Then I found CMS. Still learning around forum, youtube....
Anyway, please help me with some beginer questions:
1, About template - please correct me if I understand wrong : every page should be (or recommended) built on a template. So if in total I'll have 10 pages, 2 of them have same layout, I'll need 9 templates. And, what fields a page includes, is not defined in page, but defined in the template that page uses.
2, Where to see what modules I've installed? is it in "Modules - Site"?
3, I installed "PageTable Extended", then what? As in a youtube tutorial, it should appear in Setup tab, but it doesn't. What's in there: templates,fields,logs,comments. (I installed "Uikit 3 site_blog profile".)
4, I did a search in Processwire website for the famous "repeater matrix" module, and can not find it, there's a Repeater, as well as a Matrix. Is it not a module?
5, I watched this youtube tuts: https://www.youtube.com/watch?v=IHqnLQy9R1A
Anybody familiar with this tuts please help:
After he analysed a target webpage layout he wanted to mimic, he created some fields, some template, then based on those he created a page and input some "content" in there, then clicked "view", it's just some text. So, here comes my question, he copied a folder "assets" (subfolders are: css,fonts,js,img) over, then the page have the appearance/layout he wanted to mimic. Where does that assets folder come from?
Appreciate any help.
I've created a set of modules for importing (manipulating and displaying) data from external resources. A key requirement was to handle large (100k+) number of pages easily.
import data from CSV and XML sources in the background (using Tasker) purge, update or overwrite existing pages using selectors user configurable input <-> field mappings on-the-fly data conversion and composition (e.g. joining CSV columns into a single field) download external resources (files, images) during import handle page references by any (even numeric) fields How it works
You can upload CSV or XML files to DataSet pages and specify import rules in their description.
The module imports the content of the file and creates/updates child pages automatically.
How to use it
Create a DataSet page that stores the source file. The file's description field specifies how the import should be done:
After saving the DataSet page an import button should appear below the file description.
When you start the import the DataSet module creates a task (executed by Tasker) that will import the data in the background.
You can monitor its execution and check its logs for errors.
See the module's wiki for more details.
The module was already used in three projects to import and handle large XML and CSV datasets. It has some rough edges and I'm sure it needs improvement so comments are welcome.
TemplateEnginePug (formally TemplateEngineJade)
This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
Project in modules directory: modules.processwire.com/modules/template-engine-pug/
For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
By Robin S
Pages At Bottom
Keeps selected pages at the bottom of their siblings.
A "bottom page" will stay at the bottom even if it is drag-sorted to a different location or another page is drag-sorted below it (after Page List is refreshed the bottom page will still be at the bottom).
Newly added sibling pages will not appear below a bottom page.
The module also prevents the API methods $pages->sort() and $pages->insertAfter() from affecting the position of bottom pages.
Note: the module only works when the sort setting for children on the parent page/template is "Manual drag-n-drop".
Because you want some pages to always be at the bottom of their siblings for one reason or another. And someone requested it. 🙂
Install the Pages At Bottom module.
Select one or more pages to keep at the bottom of their siblings. If you select more than one bottom page per parent then their sort order in the page list will be the same as the sort order in the module config.