Sipho

@Robin S The client would be creating the pages. Initially, I will be migrating the pages from the old website and I shall use one of the techniques you mentioned. But it is still often easier to enter the data in a different format from editing it. Another example is names. It is more intuitive to input names in this format: But it is easier to manage and search the data using ProcessWire when it is in a format such as a repeater with a first name and last name field. I was going to try and get this special form going like I described and have the API interact with that because it would be easier. But I think I will do it the way you described instead. I am still curious as to how one would go about this though for the client.

I have an issue where I want different formats for creating one page. When you are creating a new page I want it to offer different types of fields from when you are editing it. For example, I have a field called countries which is a multiple page reference field. This is desirable as it is in a very easy to edit format. Currently, I am using selectize.js which makes it possible to search for the pages and add them in a tag fashion. This is how I want it to be when a page is already created. However, when creating a new page it is often easier to just paste a list of all the countries as text. This is because the data is coming from an old website where the countries are written like this: I can code something which converts this text into the multiple page reference fields but I am not sure how to go about it. At first I tried making another template which had fields that were in this “quick” format. Then I planned to make it such that when you add one of these quick pages it creates a page in the standard format and deletes itself. This has it’s own problems such as where to place the new page, what title and name to give it, whether to have just one quick page or multiple and when to delete it. It just didn’t seem right. Another possibility would be to show special quick fields when creating a new standard page but hide them when the page is saved and show the standard fields. I am not to sure how to achieve this though. Does anyone know a better way of going about this? I feel like this is a simple problem which already has an elegant solution.

@Robin S @rick Yep that worked. Thanks.

@kongondo Version: 3.0.62 Site modules: AdminOnSteroids ImageExtra ImportPagesCSV JqueryDataTables ModulesManager Theme: Reno

@kongondo For some reason I can't get that to show up. When I hover my mouse over it it just says "Toggle open/close".

Oh my goodness that page is so obvious. I don't know how I missed it. Sorry for wasting your time!

@LostKobrakai Well this is embarrassing . I will look harder next time.

@tpr Ah, I found it in the database. I will keep that in mind when I want to know another property. But why isn't stuff like this documented? Is there any way people can contribute to the documentation?

@tpr Yep that's worked. It returns the ids in an array. How did you find that out? I couldn't see it anywhere in the documentation.

I wish to access a template's allowed templates for it's children from the API. This one: I am pretty sure this is possible, but I can't seem to find it anywhere in the documentation. If this is not possible, is there some way of assigning properties to templates? So like fields that already have a value on all pages using that template.

So after looking at and looking at my data again I came up with the following structure: The structure is families -> family -> subfamily -> genus -> species This is how I originally thought of doing it, but I thought it would cause problems when I wanted to add new species and filter data. However, I have now realised that having a good page structure is very desirable. This way, people can link to the individual categories or browse through them but I can still have a separate page that references them and can filter through them. Thanks for the help! Also, I am loving how easy it is to use ProcessWire! It's much better than something like WordPress for a task like this. I don't have to constantly fight the system

@arjen @Sérgio Jardim Thank you for replying so quickly! I will look into both of those.

I am trying to create a sort of database system using ProcessWire. I don't want all the data to show up as pages on the website but instead pull it into pages. Similar to the Skyscrapers demo except in that one the data shows up as pages. The data I wish to store is information about types of moths. So family, sub-family, genus and species. Each of these has information associated with it. For example, species has name, images and distribution. This is another example of information about the species. Initially, I attempted to do this using nested repeaters. This appears to work but I feel there is a better and more elegant way. Additionally, this page says: So I then tried using pages with children, but this also didn't work well. I had to make every single page unpublished as I don't want them showing up in menus and other places. This means they all have strikethroughs in the admin tree which is very annoying. Is there a better way of handling this kind of data in ProcessWire or is this maybe not a suitable project for ProcessWire? I apologise if this is a silly question, but I could not find anything on this matter and am still new to ProcessWire.