Jump to content

prestoav

Members
  • Posts

    137
  • Joined

  • Last visited

1 Follower

Contact Methods

  • Website URL
    http://www.prestoav.com

Profile Information

  • Gender
    Male
  • Location
    Ely, Cambs UK
  • Interests
    Consumer tech, guitars, rock 'n' roll, classic cars

Recent Profile Visitors

2,605 profile views

prestoav's Achievements

Sr. Member

Sr. Member (5/6)

95

Reputation

2

Community Answers

  1. Hi there. Yup, you guessed it. Thank you, I can't believe after all this time I missed that!
  2. PW 3.0.165 / Admin Theme UIKit Today's head scratcher! I have 20+ PW sites running on my localhost under MAMP at localhost:8888, many of which are PW 3.0.165 / UIKIt Admin theme. Today I noticed on one site the admin 'View' links in the page tree and the page editor are removing the port number from the URL. so rather than linking to 'localhost:8888/site/page' they are linking to 'localhost/site/page'. To make things even more weird the other admin links ('edit' for example) leave the ':8888' intact. Finally, it's only happening on one site, the others on the same host are fine. I've looked at the .htaccess and there are no rewritebase rules in operation. I wondered if anyone else had seen this and figured out what that may have happened on any thoughts on possible reasons? Thanks, as always, in advance.
  3. Yup, that's it exactly, I have MultiLang installed but only one language (me default installation ready for multilang sites). I'll mark this solved. thanks for the link to that thread @wbmnfktr 🙂
  4. Hi all, I could have sworn I used to be able to use the site generic 'title' field as a sub field of a repeater field. However I've tried to do this on two 3.0.165 sites recently and, while it will add the title field in the repeater field setup, it wont save the repeater title sub field's content when the repeater is used in a page template and edited. It;'s not a big issue but I wondered if this was a known restriction?
  5. Hi @matjazp, Thank you for your help, I'm not sure I would have tracked this down without that last suggestion to comment our the hidden visibility. Long story short it was my own fault! I built this site a long time ago and, in my naivety back then, added a protection line at the beginning of the main admin.php template that redirected front end users if they were to ever stumble on a real admin page using Fredi (the previous FE editor I was using). That line was redirecting front end users as soon as FEEL was trying to open an admin page. Oddly that wasn't happening with Fredi!?! Anyway, it's now working as expected and it was my fault not the module! Thanks again!
  6. The more I look at this the more I suspect a permissions issue. It works perfectly for the Super User, just not for any other role. Checking the permissions for the 'editor' user like this, just before the call to FEEL to create the edit button: $perms = $user->getPermissions(); foreach ($perms as $perm) {echo $perm->title . " | ";} if ($page->editable()) {echo "Page is editable.";} I get this: "View pages | Edit pages | Delete pages | User can update profile/password | Page is editable." Every piece of evidence is suggesting it should work for the user but it just doesn't unless the user is a super user. 😞
  7. Hi @matjazp I'll do that as I'm really curious to see what's going on. It makes no sense that it works for the super user but not other user roles, even when they apparantly have the same permissions for page edit and creation.
  8. Thank you @MarkE, I'll definitely take a look!
  9. Hi Robin, Yes, that was my understanding too. I have been using that for quite a while without issue. The other thing I removed (which also maybe the cause but I don't think to) was the reference to the root page as $pages->get("/"). Maybe that was the 'root' cause?
  10. Thanks for getting back to me @matjazp. That's a shame it's no longer supported. I tried your suggestion of commenting out the check lines in the the .module file and go straight to the line: var editForm = iframeContent.find('form#' + (mode === 'template-edit' ? 'ProcessTemplateEdit' : 'ProcessPageEdit')); But sadly that made no difference. In the .js file it seems to come down to this bit of code failing: if (editForm.length) { if (mode !== 'template-edit') mode = 'page-edit'; processPageEdit = true; } else { editForm = iframeContent.find('form#ProcessPageAdd'); if (editForm.length) { mode = 'page-add'; processPageAdd = true; } else { // close the modal processSaveRedirect = true; setTimeout(function () { $.magnificPopup.instance.close(); }, 100); return false; } } logging editForm.length shows a val of 0. So, the process arrives at this check but has no content to work with.
  11. Finally found the issue! In the template set I was using the following in various places to retrieve the root page: $pages->get(1); In V3 that doesn't work. However, this does: $pages->get("id=1") All works as expected once those were swapped out.
  12. Hi @benbyf If you right click on the image in the CKEditor field and select "Image Properties" then click on the quote marks icon you can edit Img Alt there.
  13. I've done this for a couple clients. @mr-fan suggestion is the one I use to. One installation I've done works like this: Download Library Page (hidden, template = "downloads") - File 1 (template = "download", contains a file upload field called 'pdf_file' 'and sometimes other fields such as 'title' etc.) - File 2 (template = "download", as File 1) - File 3 etc. Then, create a "file_download" field on pages that need the files. This is a Page Reference field with parent page set to the Download Library page and the selector template="download". I use a Page Select Multiple type for this. In the page template you can then do this to get the files foreach ($page->file_download as $fd) { echo "<a href='{$fd->url}'>{$fd->title}</a> } Hope that helps.
  14. This site launched earlier this year (2021) and was the product of about 9 months work between myself and the site owners. It was a ground-up build replacing a Wordpress site. Trinnov are based in France and design and manufacturer perhaps the finest cinema processors and room correction hardware in the world. The project features multi-language, product library, a dealer & distributor locator integrated pulling data from the company's BMS, a full featured blog, a site-wide file library for manuals etc. plus a host of other features and customisations including a contact form that emails to different destinations depending on a combination of product application and enquiry type. I hope you like it! https://www.trinnov.com/
  15. Hi everyone, I'm hoping someone can help here... I've installed FEEL an added the following link in the template: $editArray = array( "class" => "btn btn-primary", "text" => "Edit This Listing <i class='fa fa-pencil' aria-hidden='true'></i>", "fields" => "title,colour,listing_type,vendor,product_type,price,price_original,bin_link,product_has_packing,product_has_manual,product_has_leads,body,page_image,product_image_1,product_image_2,product_image_3" ); echo $page->feel($editArray); When a SuperUser tried to edit or create a page then the system works as it should. However, when a non Super User tries the expected edit button appears and, when clicked, opens the Lightbox. However, at that point there are no fields presented, instead the blue spinner icon appears for a few seconds then the box closes and the page reloads with no page fields presented. PW version 3.0.165 FEEL version 1.4.0 UPDATE Digging into FrontEndLightbox.js it seems the mode is set to 'page-edit' but editForm.length == 0. Looking at the comment in the file this means that: In summary the user is logged, has edit and create permissions for the template in question but FEEL won't let them edit. Anyone see a similar issue or can point me in the right direction?? @tpr All help really appreciated!
×
×
  • Create New...