Search the Community
Showing results for tags 'admin template'.
Found 1 result
-
Hi Guys, 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?
