Leaderboard

Here is my website, built with ProcessWire, and still being refined as I learn more. https://robpackerphotography.com/ My website journey has taken me via plain html, Singapore (anyone remember that?), Wordpress, modx, and now finally PW. Along the way I experimented with drupal, concrete, silverstripe and a few others that I'd rather forget. All self-taught and done between full-time work, family and a passion for photography. I have found using ProcessWire relatively simple - despite the steep learning curve of having to learn about php... The community support is fantastic.

Hi everyone. It's been a while. A little update. There has been a delay, again, unfortunately! Lockdown hit really hard. There were also a number of technical issues but these have since been resolved. Finally, a number of you (having seen the preview videos) strongly expressed the need for the Padloper UI to resemble the ProcessWire admin theme even in the alpha stage. The message I got was that this was more important to them from the get-go than having advanced Padloper features. I accepted their reasoning but this came at a cost. Padloper 2 has been re-themed to look like the ProcessWire admin. Given that we are using third-party libraries to build Padloper 2, this took a lot of time. Focus was placed on basic features only, for now, in order to expedite the first release of Padloper 2. This means that some advanced features will be missing from the first release of Padloper 2. As for a release date, I was hoping for a 'spring baby'. That won't happen. I am now working hard toward a 'summer baby'. Screenshots Have a nice and safe day.

You can use multiple instances of processwire and include one in another. $pwComments = new ProcessWire($config->paths->root . 'site-comments'); $home = $pages->get(1); $homeOfComments = $pwComments->pages->get(1); https://processwire.com/docs/more/multi-site-support/ use Option #1 https://processwire.com/blog/posts/multi-instance-pw3/#using-multi-instance-in-pw3 This is also possible under a single domain if you do not need a frontend at one of the two installations and use different names for your /admin/ pages and session cookies. Under special circumstances you can also access the current user of one instance within the other. Look here: https://github.com/processwire/processwire-issues/issues/1294#issuecomment-759351593

@benbyf I'm still using it without issues! And even use it with @bernhard's RockMigrations . I think there is an issue with the composer install related to composer 2, but you should be able to install it like a normal module. EDIT: @benbyf dude I completely tripped and was thinking I was in the old Migrations module thread lol Nonetheless, I have also used this project a lot and noticed it breaks with most recent php version, I think 8+

Thanks for your hard work, I can only imagine how complex it is to build a system like this.

Also the videos! Good work. And also impressive is the copyright notice 1981 - 2021 ? ?

Very nice photos!

@kongondo keep up the great work. For me it would just be great to play around with this and service the ecommerce requests that I get, even in a basic capacity knowing that a fuller feature set will come later so I am not too fussed about advanced features at this stage.

Great work! Can't wait ?

I think it's a good idea and plan – plus if your main site is cached with something like procache, you could load user comments via ajax from the subdomain "user" site. I'd probably do it the same way as you; It's sort of like making your own version of a commenting platform which is integrated into the site, like Disqus or something. And if eventually at some point you had a huge user base, you could run the entire subdomain on a different server.

Miss Monique (on YouTube)... awesome sets.

Generally speaking PHP 7 and 8 tend to work similarly in these situations — PHP 5 was more "forgiving" ? Anyway, it could be related to VC 1.3.1. I've been using VC 2.x for a very long time, will have to set up a test site for 1.x. Edit: turns out it's an issue affecting PW < 3.0.166. At least this particular instance of it is pretty easy to circumvent; I've prepared a fix, but will have to test carefully before releasing it.

WOW!! Really awesome! Cant wait to see it in action... @kongondo when do you think it will be released?