Jump to content

kongondo

PW-Moderators
  • Posts

    7,159
  • Joined

  • Last visited

  • Days Won

    137

kongondo last won the day on June 19

kongondo had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location
    UK

Recent Profile Visitors

32,326 profile views

kongondo's Achievements

Hero Member

Hero Member (6/6)

8.1k

Reputation

78

Community Answers

  1. @Greg Lumley, Just to be clear, did menuRender() used to work in an older site but isn't working in a newer site? If yes, what is the difference between those sites in relation to: ProcessWire versions? <-- I suspect the issue is here perhpaps. PHP versions? Thanks.
  2. @xportde. Thanks for catching this. I'll work on it, hopefully soon. I am (very) slowly moving all my modules to require at least PHP 8.x. Thanks!
  3. Thanks for this example @Tyssen. Out of curiosity, how do you use $currentID subsequently?
  4. Hi all, Sorry, I have been away from this parts of the forums for a while. @Clarity I am not sure I follow. Please clarify, e.g. with an illustration. Does this post perhaps offer a solution?
  5. Hi @Spinbox, Thanks again for catching and reporting this as well as providing a test environment. The issue has now been fixed in today's release (007). As stated in our communication, it was caused by Padloper uninstaller not checking for Padloper items in the trash. This would cause a fatal error when attempting to delete the Padloper templates still in use by the Padloper items in the trash. Version 007 is ready for download. Thanks!
  6. I have tested with Padloper 0.0.5 and it still works OK. I think it's time I had a look at your site, if that's OK. I'll PM you with more details, thanks.
  7. Hmm. This is very strange. That error message is not one that is related to Padloper uninstall/removal actions. It is related to edit actions (bulk, single page, etc). I have tested with Padloper 004 and it works. Could you please confirm which Padloper, ProcessWire and PHP versions you are testing on? Thanks.
  8. Hi @alexm, This is now possible in version 006 released today. You can hook into PadloperProcessOrder::getOrderCustomer. Demo code is here including comments in the code and a README. Give us a shout if you need further help with it.
  9. Had you attempted to remove some stuff manually before this? I am happy to have a quick look if this is a remote site.
  10. Hi @Spinbox, Please follow the instructions detailed here.
  11. I see. In that case, you need to be aware of Shopify API rate limits (if you are not already 😀).
  12. Hi @Nomak. Welcome to the forums. Is this a one-off? If yes, another option is to export the products (in the Products Dashboard in Shopify admin) as CSV and then use that to import the products into ProcessWire. At that point you can use the ProcessWire API + PHP to do the imports or modify the CSV and use a module such as ImportPagesCSV to import to ProcessWire.
  13. Hi @alexm, Excellent! Glad to hear that! Will have a look, thanks for letting me know.
  14. Yes, that is the plan. The docs and the demo will be here. However, the purchase might remain at processwireshop.pw.
  15. Late to the party but I agree with the approach by @rick. This is a database layer issue and I would approach it with a database solution, in the first instance, instead of a code one (hooks, forcing IDs, etc). Given, the forceID flag was added for a reason but for an operation of the scale and intricacy you are dealing with, I'd let the database handle IDs. The 1M idea is clever but given that you are enforcing it through code, it takes one or two mistakes/glitches and you could end up with some 'lost' users (e.g. with IDs < 1m).
×
×
  • Create New...