BitPoet

Members
  • Content Count

    804
  • Joined

  • Last visited

  • Days Won

    36

BitPoet last won the day on October 8

BitPoet had the most liked content!

Community Reputation

1,899 Excellent

1 Follower

About BitPoet

  • Rank
    Hero Member

Profile Information

  • Gender
    Male
  • Location
    Near Munich / Germany
  • Interests
    programming, writing, scuba diving, long distance hiking

Recent Profile Visitors

5,056 profile views
  1. There is already an open issue about this with a workaround.
  2. BitPoet

    You can do that using the multi-instance feature of ProcessWire 3. Have a look here.
  3. Take a look at the raw http response body in your browser's developer console. My guess is that some kind of error/warning output from PHP (perhaps a configuration conflict in php.ini or a PHP version issue) performs some early output and thus prevents sessions and login from working. But the raw response should contain some kind of hint about it.
  4. BitPoet

    Status update: Release 0.1.3 I finally managed to implement hiding libraries from the page tree as requested in the issue tracker. This can be enabled in the module configuration and optionally extended to superuser. Deletion of libraries is now possible through the Media admin page.
  5. BitPoet

    Sorry, I missed this question. I hope this has meanwhile been solved. This looks more like a generic ProcessWire issue, since the upload uses core functionality and the symptoms sound familiar from regular image upload (memory issues or PHP limits).
  6. Why call $pages->find at all? foreach($page->fieldname as $child) { should do the job.
  7. BitPoet

    The reason (at least how I read ryan's responses to questions about the options field type) is that more often than not, a page field is the better (i.e. more flexible and extensible) solution when you want to allow the user to make a choice. Having the field type installed by default would probably tempt users to start using it right away without learning to appreciate the power and ease of page fields. There are a few use cases for the options field type, like simple dropdowns in frontend forms (that's where I use them). But a page reference field supports drag&drop reordering of options for editors, it's easy to give the template for the selectable pages a PHP template too to list all pages with that option, you can publish and unpublish "options" without deleting/adding them, regular editors can do that (and add/remove options) without a need to mess with the field's configuration, and the API side is much more intuitive and flexible too...
  8. @jmartsch: are these admin pages regular pages open in ProcessPageEdit, custom Process modules or pages added through AdminCustomFiles? In each of these cases, the answers might be a bit different.
  9. Each students and pets table is its own template, each row a page. For a limited set of repeating information like your pet type, a page reference field is most often the way to go. The "pet type" pages can live anywhere in the page tree and can optionally have a PHP template to list all pets of that type. The pets-students relationship can be defined as a page reference field linking from the pet to the student, from the student to the pet or, if you plan to implement complex selectors later on, using the Connect Page Fields module also both ways. The page reference fields can be limited to only show pages with a certain template (student, pet, pet type). Names and age should be regular (text, integer) fields. You could re-use the mandatory title field for the student and pet name and just change the label for it in the individual template's settings. I'd probably also create a "pets" and "students" template (plural) under which the individual entries live in the backend to keep things sorted and allow outputting lists. Home (or another common parent page) Students Heather Rachel ... Pets Rex Thomas ... Pet Type Dog Cat ...
  10. BitPoet

    I sent him a PM to be sure, new threads and mentions are probably easy to miss.
  11. And here's another update: I worked on history support. Now each time a document is saved, the "old" version is saved away (under site/assets/cache/.loolversions/$pageid/ with a unique hash as a name) and an entry is added into the versioning table (lool_versions). These versions can already be listed in the UI (File -> Version history opens a sidebar at the right). Also, the UI language for the editor can now be set in PW's profile settings. If you feel daring, you can grab the latest dev branch and take it for a test drive.
  12. BitPoet

    Looks like there is an include:sendgrid.net missing in processwire.com's SPF record. Your mail admin might be able to add an exception for processwire.com, but since there is a hard fail policy in the record, @ryan needs to change that in his DNS (or perhaps he has already done so but the change hasn't propagated to the DNS servers yet).
  13. Update: I finally found a little time to work on the module. The WOPI endpoint (the "server" script that LibreOffice Online talks to) is now created by the installer. Also, there was a bug when PW was installed in a subdirectory, which has been fixed. The next thing I'm going to work on is revision history. This is quite underdocumented territory, so hold your fingers crossed
  14. Somehow your reply slipped by me. In case it's not too late: docker really is fairly simple if you have a reasonably current platform. I have it running on Ubuntu 16 inside a VirtualBox VM and on a recently installed Ubuntu 18.04 server. In both cases, it's little more than running "apt-get install docker". To get Collabora CODE installed and running is quite smooth too, though you have to look out for one or two pitfalls. The first step is always running "docker pull collabora/code". This command should get things up and running on the CODE side: server_name=my.host.name docker run -t -d -p 127.0.0.1:9980:9980 -e "domain=my\\.host\\.name" --restart always --cap-add MKNOD --add-host="my.host.name:my.hosts.ip" collabora/code Of course you have to replace my.host.name with your official hostname (same for my\\.host\\.name) and insert your real IP instead of my.hosts.ip. For the latter, use the internal IP if your server is behind a NAT. Any environment settings ("-e" arguments) are usually documented in the docs for the individual docker image. Docker will take care of restarting your container when the docker service itself is spun up. You can see your running docker containers by typing "docker ps". The output will end with some fancy name (like "lucid_pike") here: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1e5ed6b3922c collabora/code "/bin/sh -c 'bash st…" 18 hours ago Up 18 hours 127.0.0.1:9980->9980/tcp lucid_pike This name is used to point other docker commands to the instance. You can e.g. view its logs with "docker logs lucid_pike".
  15. That's a limitation. The URL field type (which AssistedURL adds JS sugar to) doesn't store a page id for underlying URLs, so it has no way of knowing that the link is an internal one and that the URL has changed. I solved that problem by using a radio button that switches between the URL field (for non-PW links) and a regular page field. That's not perfect, but it works so far (quite a few years by now, actually) and I haven't had any user complaints.