Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


digitex last won the day on January 24 2012

digitex had the most liked content!

Profile Information

  • Gender
  • Location
  • Interests
    Artist, designer, photographer

Recent Profile Visitors

4,364 profile views

digitex's Achievements

Sr. Member

Sr. Member (5/6)




Community Answers

  1. There's nothing in the log which is expected, it didn't throw an error it just doesn't display the drop downs etc. The console shows the error: Uncaught Error: Invalid LatLng object: (NaN, NaN) Not sure that error is related. I've decided to include leaflet the old fashioned way and bypass the module. I've done that many times.
  2. I've got this module installed into pw 3.0.184 and noticed a strange bug. When editing a page in the admin containing the leaflet field the dropdowns in the header for settings, modules, access and the user drop down disappear, as does the Save button. Once I delete the field from the template things return to normal. It seems there's a js conflict somewhere. Just a heads up to @Mats.
  3. I'll put that on my to do list. I don't have a GH account yet so I'll have to set that up first. @adrian done. Thanks for the suggestion. Turns out I did already have GH account, it's just been so long since I logged in I had forgotten.
  4. While we're on the subject of comments 😋 I have another question. When notifications come in, I have never seen any actions other than "approve now". Many comments are not useful to the public, to say the least, so an admin won't want to approve but to do anything else requires logging in to manually mark as spam or delete. This kind of defeats the purpose of moderating directly from the notification email and if you do nothing the comments remain pending and clog up the system. I found the code in CommentNotifications.php that deals with moderation actions but I'm not certain how to add to it. if($comment->status == Comment::statusPending) { $status = $this->_("Pending Approval"); $actionURL .= "approve"; $actionLabel = $this->_('Approve Now'); } else if($comment->status == Comment::statusApproved) { $status = $this->_("Approved"); $actionURL .= "spam"; $actionLabel = $this->_('Mark as SPAM'); } else if($comment->status == Comment::statusSpam) { $status = sprintf($this->_("SPAM - will be deleted automatically after %d days"), $field->get('deleteSpamDays')); $actionURL .= "approve"; $actionLabel = $this->_('Not SPAM: Approve Now'); } else { $actionURL = ''; $actionLabel = ''; $status = "Unknown"; } Having the option to mark as spam on a pending comment seems like it would be very useful.
  5. I figured it was tracy, I was just marvelling at how much easier it is to read than phpMyAdmin. I found a solution here: This works. It's an odd behaviour for the Approve Now button in the notification email to only work when comments are rendered through the render function. I can work with it though 😂 Thanks for your help.
  6. Thanks for the hint @adrian. The interface looks very different on my end but I found the settings. Seems my problem is different in more than one way: the schemaVersion is already set to 6. I don't see a message like you described, the approval email simply does nothing when clicking the approve link i.e. pending comments remain pending. I had hoped your issue and mine may have had a similar solution.
  7. Can you narrow things down for me adrian? I'm having the same problem but there's a lot of code to go through and I don't know where to look. Please.
  8. Does fieldType PDF support tags? You can configure tags in the field set up but I get an error when I check for them with $pdf->getTag(). Edit: The field is fine, I made a mistake in how I was retrieving the tags, forgot that in order to get the tags as an array it should be $pdf->tags(true); and so the way I was doing it was the problem.
  9. @Robin S I just installed the latest version and upgraded from 1.9 to 2.1 (this morning). BRILLIANT!!!! Beautifully done. It works perfectly. Thanks again for a very handy module.
  10. No it doesn't. I have other fields that do fill in when field visibility is conditional but not in this case. I don't know why but when the field in question is not displayed, the other field beside it, set to 50%, stays at 50% and the fields in the next row flood in and alter the layout, in a bad way. I'm using this module because I need a custom selector and it's very handy. I got around the problem by giving both fields 100% width so not a big deal.
  11. @Robin S This is a very handy module, thank you. I have a situation that is inconvenient at best but has me wondering. I have 2 fields set side by side on the template with 50% width and a showif condition that means one of the fields only appears occasionally but when it's not visible the layout goes to hell since the first field is set to 50% width. Is it possible to expand this module to include the column width so that if the same selector that determines visibility is met the column width would change from 50% to 100% to fill in the row? If so it would allow for field visibility to change without effecting the rest of the layout. that would be awesome.
  12. @Robin S Thanks for that. I didn't even know those options were there. I agree percentage based should be default.
  13. @adrian Yes I read through that thread, maybe not every post, it's a whopper. I didn't see any post addressing the big incompatibility I mentioned above. I like the look of UiKit better than the default, it's more modern and slick but I used to enjoy being able to set custom widths in unconventional setups e.g.: Model Name (50%) Secondary Name (checkbox 15%) Second Model Name (visible only if checkbox is checked 35%). All widths equal 100% but it doesn't work with UiKit (I tried) which is a bummer but mostly frustrating because I have the ability to set those weird, unconventional widths due to the column width config being a slider that uses 1% increments. If it's not possible to make UiKit work with any custom width combo then the slider should probably not be there encouraging it. A minor gripe.
  14. I'm still experiencing problems with UIKit and column widths. One of the biggest selling features of PW is that it "makes no assumptions on how you choose to work" which is very powerful but now thanks to UIkit it is dictating how templates are laid out. The biggest issue is that there is a column width slider that allows adjustments in increments of 1% which is clearly not supported by UIkit. Maybe it's time to ditch the slider and replace it with a series of radio buttons allowing between 1 to 6 columns so admins don't start making custom adjustments like they used to be able to do.
  15. I'm getting this now. I installed an SSL certificate to log in securely and now I get this error. Only thing is, the site is old, first done in 2013 with PW 2.X so the site config file actually has no $config->httphosts setting. I added it to the config file and it seems to be working.
  • Create New...