Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

39 Excellent

About Tyssen

  • Rank
    Distinguished Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Brisbane, Australia

Recent Profile Visitors

4,692 profile views
  1. So I've kinda got stuck with this which I've described in another thread:
  2. I want to be able to use the page that a user is assigned to do other things in my templates. If I do this: $ap = $user->editable_pages; echo $ap; I get a number output. But if I do this: $lp = $pages->get($ap); echo $lp->title; I get an error: Unknown Selector operator: '[empty]' -- was your selector value properly escaped? If I hard code the actual number from echo $ap in the get selector then I get the output I'd expect. What do I need to do to $ap recognised as a PW page object?
  3. Ah, that's an interesting idea and probably less work than what I had in mind, lol. Except in my case, the member group is assigned to a portfolio page via a page reference field, rather than being assigned to the user. And the user is given edit access to his/her page with the Page Edit Per User module. I can still work out which member group page a user is associated with, it just won't be as straightforward as using hasRole.
  4. I've been brought in to work on a site which allows members to upload images to display on their profile page. The number they can display is limited by the member group they're in. Currently, the limit is only applied on output, not on input. The same image field is available to all members so they're all getting the same upload limit.. I'd like to change it so that each member group has its own images field and each field has the upload limit set to the limit for that group. I know I can use field dependencies to show the correct image field depending on which member group they choose. But how do I get the existing images that are attached to the current all-in-one images field into the new member group-specific image fields?
  5. I've just installed Valet and have been testing sites running a few different CMSs including PW, Craft and ExpressionEngine. The sites on Craft and EE work fine, but for one of the PW sites I created, I get the home page on every URL I visit, and the other, the home page works OK, but every other page gives me a 'The page isn’t redirecting properly' error. Actually, it's every other PW page, i.e. one ending with a / If I try and visit a non-existent page like example.html, I get the 404 page for the site. Is there something else that needs to be done to PW sites to get them to work with Valet?
  6. I've added a function to my _init file but found it wasn't working until I added a namespace to _init and any other file calling a function from _init. But on one template I've got new SimpleXMLElement which is causing the 'class not found error' which appears to be due to the namespacing. What do I need to do to solve that?
  7. @gmclelland Must've been something wrong with the export of the db from my local. I renamed MarkupSEO and then it threw the same error for FormBuilder. Renamed it too and then the admin page came up but using the default theme and it was reporting that modules had been downgraded to earlier versions. Ran another export/import and it's all fine now. 😕
  8. @flydev I still get the same error. I should also mention that this staging site was working fine until the latest changes.
  9. I've been working on a site locally and wanted to upload some changes to a staging site but after exporting the site's database and reimporting to the staging site and uploading the changed files, I can no longer access either the front or back end of the site. Instead I get: I've tried deleting the contents of site/assets/FileCompiler but that didn't help. What else do I need to do to get the site back?
  10. Tyssen


    Actually it is. I've just checked wire/core/Fields.php and the added lines from the commit you linked to are already there.
  11. Tyssen


    I've upgraded PW to 3.0.141 and the module to 0.9.0 but still get the same error I reported on the previous page when accessing a page which has the field in its template.
  12. Tyssen


    That solves the editing of the field problem, but if I visit a page which has the field on it, I get:
  13. Sorry, I had Use parent's values if empty checked previously and those fields didn't show until I unchecked it. All good now. 👍
  • Create New...