Recently Browsing 0 members
No registered users viewing this page.
I have been using Processwire for years now and have mastered enough to create some amazing sites and applications.
However, recently I have been thrown a bit of a curveball and hoping some more veteran members can chime in.
I recently ran into a weird issue. I had imported about 100+ wordpress pages into a new Processwire site using namespaces.
I imported them under a parent page called /landing-pages/.
However, I needed to move 20+ of these imported pages to a new parent page called /customers/.
Since I was moving so many, I figured batcher was a solid module to run this task.
Here are the steps I took:
Located all the pages I needed using batcher Changed the pages templates Located the pages again after changing their template Made the pages hidden and then located them again using batcher Changed parent page from /landing-pages/ to /customers/ The issue that occurred is that not only did I change the parent page for these pages but apparently the pages also existed under /admin/repeaters/for-field-whatever which now changed to the new parent of /customers/.
for-page-1625 admin /admin/repeaters/for-field-108/ So I reverted this by using batcher again, here are the steps I took:
Located all the pages that were not supposed to be moved Changed the pages parent back to /admin/repeaters/ The issue is, after this was done, every time I clicked the new page under /customers/whatever-page I would get a 404.
To correct this I had to delete all the pages under /admin/repeaters/ and /admin/repeaters/for-field-whatever and then go back and delete the pages under /Customers/ and create them all from scratch.
My questions are:
Why did Processwire create pages under /admin/repeaters for the imported pages? The steps I took to correct this issue, is this okay to keep building the site or am I better off starting fresh again?
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.
I've upgraded one of my pw 2.7 websites to the 2.8 legacy version and I'm encountering some problems.
As you can see in the image I don't see uploaded images thumbnails anymore, and the repeater fields previously added are no more usable.
Why I'm having this strange behaviour simply after an upgrade from processwire 2.7 to 2.8?
Hope you can help me, I'd like to use the 2.8 version features like the front-end inline editing, but it seems like I'll be locked in the 2.7 version forever
this is my first topic and I need to say thanks to @ryan and all the other contributors for this incredible framework that changed my life as a web dev!
But now I go to the point. I developed a project with pw 2.7 and it worked like a charm.
Today i'm trying to update the project to pw3 on a local environment, to test that everything will continue working after the upgrade, and that's not the case.
The major bug I'm encountering is that repeater field doesn't work properly.
Existing Repeater field
This is what I see when I try to edit a page that already has a repeater field (Brand concepts) with some elements:
If I click on one of the "... blocks" nothing appens.
New repeater field
If I create a new repeater field and assing it to a template, when I open a page with that template I see the new repeater field, but the "Add new" link, to add a new element, doesn't work. I click it and nothing appens.
I never had this kind of strange behaviours in PW, and this is one of the reasons why I consider it the best cms/framework I've ever used.
I hope you can help me.