I've started using IndexMenu to implement an automatically updating index for my wiki. Now, I have implemented indexes on all front pages of my (sub)namespaces, but have run in to the problem of how to meaningfully add pages at this point.
To me, the whole idea of creating pages in a wiki was to create an empty link on an index page, follow the link and fill it with content. Now that the indexing is being done by the plugin, I wonder how I can still create pages within the wiki backend without resorting to create the pages in the actual folder structure.
Am I just completely missing something here?
I think I'm having trouble understanding the question, you can still create pages by creating/following a link - but you might find this plugin useful:
https://www.dokuwiki.org/plugin:addnewpage
If you install it and add {{NEWPAGE}} to your sidebar.txt, users will be able to create a page anywhere they have permission for.
Related
For the construction of an extensive list of links, since the source page is a thematic portal, I am looking for a suitable EXT., Which also runs under TYPO3 7.6 LTS.
it if the list of links to a permits the use of categories and multiple categorization of links is possible would be nice. should Weiterrhin the links are described not only the destination address and an alias but here should still an outline of the target page (possibly with photo) be possible.
Additional functions such as proposing links by users, reporting broken links or even a User Voting would nice additional features.
There were times the Modern Linklist, but they were no longer being developed for TYPO3 <6.x.
Is there perhaps somewhere an alternative or as one might like to vorhnandenen solutions might realize? It would be nice of course, without any programming knowledge, since I'm not a programmer.
P.S .: It is not about building a spam list but high quality links with topics relating to the original page.
As this seems to be a straight forward usage you could try to build that extension by yourself with the ExtensionBuilder.
just build up the records neccessary for your data. and let the EB generate all usefull actions: list & show, even create, edit, delete in FE would be possible.
Afterwards you just need to edit the generated fluid templates.
these links may help:
Overview
EB manual
small remark: if you want the newest code state, use the EB from git instead of TER
I`m not aware of an existing extension for it but it could be a good project to learn extbase / fluid.
You should also take a look at
typo3/sysext/fluid_styled_content/Resources/Private/Partials/Menu
and
typo3/sysext/fluid_styled_content/Classes/ViewHelpers/Menu
Fluid Content contains everything you need to create a list like that, you "just" have to combine the necessary bits and pieces.
You can do a lot with TYPO3 core functionality: there is a page type "external URL", pages can have categories by default, there are plenty of menu options (TypoScript HMENU, menu content elements, Fluid menu Viewhelpers). The Linkvalidator can periodically check all links and report broken links.
For suggestions you could add a form. Powermail for example can also store submitted info in database records, so your visitors could prepare page records (they are hidden until you make them visible).
I am new to typo3, i am trying to create a new backend layout for my home page.I need add few custom sections to edit contents.I am not able to find option to do so.
TYPO3 7.2 is out of support and has know security issues. Please update to 7.3 at least.
You can create backend layout records in any folder in the page tree. To select those backend layouts, you have to add this folder as the general record storage in the page properties of the page where you want to use your backend layout.
I suggest you take a look into the Getting started tutorial which will walk you through your first steps.
http://docs.typo3.org/typo3cms/GettingStartedTutorial/
In case you use a distribution, it might be that the backend layout is added in another way, e.g. via TSconfig or directly using PHP. Please consult the according documentation of the distribution in this case.
Figured out myself.
Go to List in Web, then click on add new + icon, then select Backend Layout under System Records.
I'm developing a website for a magazine using Ghost (http://ghost.org/) and would like to have pages that display posts from two related tags. Eg. "Science and Environment". I understand that when using a static page you do not have access to posts so I cannot for example do this. This would however be the ideal solution.
{{#foreach posts}}
{{#has tag="science, environment"}}
do thing
{{\has}}
{{/foreach}}
I have had a look on the Trello roadmap (https://trello.com/b/EceUgtCL/ghost-roadmap) but couldn't spot anything there. I would appreciate any help on a workaround.
Cheers
This is possible but a bit tricky
You should install self-hosted Ghost . There is a lot of step-by-step manuals how to do this on Amazon, DigitalOcean, Heroku, etc.
You should create your own custom Handlebars helper for your purposes.
Create myhelpers.js in the Ghost project root and put your own helper code here. For example: {{bytag}} helper which selects posts by one tag. You can extend this to query posts by more than one tag.
At the beginning of config.js place require('./myhelpers')();
to activate your custom helper.
Restart Ghost
Is there any existing way to generate a what-links-here report for a gollum wiki? In other words, a list of the pages within the same wiki that link to the current page: a list of the local inbound links.
I wasn't able to spot any feature like this, nor find anything suitable in the API, but I may have missed it. Is there a third party add-on for it?
I do understand the reason it probably doesn't exist in the core: as these are plain text files, there isn't any table of links maintained anywhere. For the same reason, when a page is renamed it breaks all the inbound links to that page from other pages.
A function for this could use the API to read the generated source of each page (so that only html with normalized names needs to be parsed), producing a list of the local links from each page and the page they are on. Cache the results at page level until the next commit of that page.
This could be used to enhance the existing page rename feature as well. Has anybody already done this?
On a website, I have a section where I put a new page every week. I'd like to convert this to a system using tt_news. How do you suggest me to import the pages (more than 100 pages) to tt_news? Can I do it using a simple SQL query, or should I write a custom PHP script to perform the importation? Is there already an extension that exists that could help me performing this task?
It doesn't really matter to me if I simply build news liked to existing pages, or if I transfer the content of the page to the content of the news. It would be great if I can convert the page title to the news publish date, but I could use the page publishing date as well.
What do you suggest for performing this task?
I would do it via SQL as you mentioned already. Could get tricky if you have multiple content-elements per page that needs to be merged into one tt_news-dataset.
You could also install an extension, that links tt_content-elements with tt_news-records. This way you only have to insert the tt_news-records by traversing the pages and link the content per page to the new tt_news-record. Here are some extension, that link tt_news with content-elements:
ttnews_irre
aba_ttnews_content_con
Here is also an extension that could be worth a look: content2news.
Hope this is useful to you.
Best regards,
Peter