Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

50 Excellent

About alexcapes

  • Rank
    Sr. Member

Recent Profile Visitors

3,706 profile views
  1. Running PHP 7.3.1 with the latest version of Jumplinks return a blank page for me. PHP 7.2.14 seems to work fine.
  2. Hi, I've been invited by Apple to use their 'News' service for a publication in the UK. https://www.apple.com/uk/news/ A number of CMSs already have plugins to publish content via the API, however Processwire is not one (yet!) https://newsresources.apple.com/en/faq/66346243 It's slightly beyond my technical abilities but would be very interested in anyone that is willing to look at developing a Processwire Module. (for reference here is the Apple News API documentation) Update: Chapter Three have created a PHP Apple News library here https://github.com/chapter-three/AppleNewsAPI
  3. Digging a bit (and by that I mean actually looking at the source!) it looks like this is not a SmartyPants issue. I can see that the double quote is being encoded by Processwire incorrectly as a right double quotation mark. <p class='review'>&#8221;<i>How Music Works </i>is a melange of bookish musings on how music is shaped by the places it is played and the technology used to create and disseminate it”<br/><span class='review-source'>Danny Eccleston<br/><em>mojo</em></span> However the data source for this content (an XML file) the quotes look just to be normal double quotes <Text><![CDATA["<i>How Music Works </i>is a melange of bookish musings on how music is shaped by the places it is played and the technology used to create and disseminate it"]]></Text> So I'm not sure why Processwire would encode (incorrectly) the first double quotation mark (if before an HTML tag) and no others?
  4. Hi, I have an issue when using the SmartyPants Typographer text formatter. If the text has an HTML tag (such as italics) straight after the quotation mark, it reverses it. So for example: This only seems to occur when an HTML tag is placed at the beginning. Does anyone know how this could be corrected?
  5. This would be for super-users only as last resort to fix mistakes. I think using 'Version Control' may be a workable solution although it does feel a little like using a sledgehammer to crack a nut - I don't really need/want version control and it might add too much complication for the client - and I only need this 'restore' option on one single pagetable field. Just to note I don't think changelog offers any way to 'restore' the a previous state of a field. *Update* Version Control can be switched on for specific fields only so I think this is going to be a workable solution for me. Thanks @Robin S *Update #2* Looks like Version Control is not compatible with PageTable fields.
  6. Thanks @Robin S I'll have a play around and see if I can get something working.
  7. RT @processwire: New post: Building the Canongate website with ProcessWire, by Alex Capes @alexandercapes – https://t.co/kH9VBPwMAu

  8. I wonder how difficult it would be to store the relationship info somewhere else and then add the page back to the PageTable if restored? Do you think it's doable with a simple module?
  9. Hi, I've noticed when I trash pages from a PageTable field, then restore them, they are restored to their original location, however the connection is broken with the PageTable field. Is this expected behaviour? Is there a way for it to maintain this relationship? Otherwise restoring it doesn't actually restore it to it's previous state. Note that in this case the parent pages for the PageTable field is not set as the direct parent.
  10. Hi, I just updated a site to 3.0.61 and it's breaking uploading images from a URL via the API. I get the following error: Recoverable Fatal Error: Method ProcessWire\Pageimage::__toString() must return a string value The code getting the image is very simple: $new_edition->work_cover = $cover_url; $new_edition->save('work_cover'); It works fine on 3.0.42 but returns the error on 3.0.61
  11. I've updated my code to remove ? ( ) from the selectorValue $q = preg_replace('/[?()]/', '', $q); However I wonder how many other characters may possibly break the search and whether there's a better way to sanitize?
  12. Hi, I have a site search working correctly on a project, however I seem to be having issue when the search term contains characters such as question marks or brackets. I'm doing the following... $q = $input->get->text('q'); if($q) { $input->whitelist('q', $q); $q = $input->get->selectorValue('q'); } $matches = "search_cache~={$q}, sort=-publish_date"; This works correctly for everything except searches that include characters such as ? or ( ) So for example a searches for the following (where the page title is "example title?") example title example title? The first one works as expected and the second returns 0 results. As the titles are very specific for a user to search, I need to make sure the search works with these kind of characters. How can I make sure search works with these kind of characters?
  13. @Robin S you're my hero again for this module! Seriously every time I think of something I need in PW you're already on it.
  14. Thanks @adrian. For those looking for this module, it's still here https://github.com/ryancramerdesign/ServicePages but needs a few small updates to work with PW 3+ (see above thread).
  • Create New...