digitex

Members
  • Content Count

    196
  • Joined

  • Last visited

  • Days Won

    1

digitex last won the day on January 24 2012

digitex had the most liked content!

Community Reputation

55 Excellent

About digitex

  • Rank
    Sr. Member

Profile Information

  • Gender
    Male
  • Location
    Ontario
  • Interests
    Artist, designer, photographer

Recent Profile Visitors

3,566 profile views
  1. digitex

    As far as I know Leaflet use OpenStreetMap which is not google. With the new changes to google maps I'm sure more people will turn to OpenStreetMap so some day with the uptick in usage they may become a pay service as well but not yet. I should also add I am converting all google maps over to leaflet. It has fewer styling options but looks good and works very well.
  2. digitex

    Hey Adrian, I'm sure I must have had it config'd wrong but I needed something quick so I just went with a front end option. I uninstalled already.
  3. digitex

    Yeah I have the same problem. Except no matter what settings I put in config I can't get options to appear and when I export the csv I get a completely blank file. It looked promising. Maybe it's not compatible with pw 2.8.62
  4. digitex

    I fixed it in phpmyadmin. I haven't seen this behaviour with Import from CSV before either. If it's not a bug, and it likely isn't, the fact that the space doesn't appear in the admin when it does appear in phpmyadmin and effects sorting, I think is an issue.
  5. digitex

    I know what the problem is. I went into phpmyadmin and looked directly at the field value in the table. Most of the values have a leading space before the street name, the ones that do not are the ones appearing at the tail end of the list. The space is not visible when you view the field in the admin. @ryan Is this a bug in the Import Pages From CSV module? The CSV file I imported had no leading space and I did a zap gremlins (BBEdit) before import. Although I can't verify that the zap gremlins command actually did what it says it will do. Is there an easy way to fix it or do I have to go through manually and remove the space? Edited to add: @wbmnfktr I was drafting this post as you were posting your question. You got it. A phantom space in the database.
  6. digitex

    No I get the same result when using street directly in the selector. I did try it with the limit removed which effectively removes the pagination as well. If there's something different about the wrong sorted entries I can't see it. They were all imported by csv at the same time from the same file created in the same way. The server it's on is the dev-environment. I just moved the necessary files to the root when publishing. I also tried foreach($members->sort($sort) as $member) { echo "<li class=\"member-item\"><div class=\"member-name\">{$member->last_name}, {$member->first_name}</div><div class=\"member-address\">{$member->street_number} {$member->street}</div></li>"; } Which did not work either.
  7. digitex

    I'm having trouble with custom sorting by field value. On a page behind a login wall I have a list of members that sort by last name A-Z by default with a drop down select to allow users to change the sort to last name Z-A or by street. The last name sort works but when sorting by street, which is just a text field containing a street name in title case, I get very odd results. It will sort A-Z by street name but omit some of the members and stick them in at the end, also in alphabetical order but separated from the rest. As far as I can see, there's nothing different about the values in those fields, I even cleared a few and re-entered the data to see if there was some gremlin character in there, but no effect. To illustrate: Street: Alpha St. Beta St. Foxtrot St. Golf St. Michael St. Tango St. Uniform St. Whiskey St. Alpha St. Foxtrot St. Hotel St. Tango St. The code is: <?php if($input->get->order) { $us = $sanitizer->selectorValue($input->get->order); $input->whitelist('order', $us); if($us == "az") { $sort = "last_name"; } elseif($us == "za") { $sort = "-last_name"; } elseif($us == "add") { $sort = "street"; } } else { $sort = "last_name"; } include("./head.inc"); ?> <div class="container"> <div class="member-directory"> <?php echo "<h1>{$page->title}</h1>\n" . $page->body; $members = $pages->find("template=user, roles=member, limit=100, sort=$sort"); $paginate = $members->renderPager(); echo "<div class=\"page-controls\">{$paginate}\n"; echo "<div class=\"filter\">\n <select onchange=\"window.location.href=jQuery(this).val()\" name=\"order\" id=\"order\"> <option value=\"?order=az\""; if($input->get->order && $us == 'az') { echo " selected=\"selected\""; } echo ">Alphabetical A-Z</option>"; echo "<option value=\"?order=za\""; if($input->get->order && $us == 'za') { echo " selected=\"selected\""; } echo ">Alphabetical Z-A</option>"; echo "<option value=\"?order=add\""; if($input->get->order && $us == 'add') { echo " selected=\"selected\""; } echo ">Street Name</option>"; echo "</select>\n</div>\n</div><!-- end of page-control -->\n"; echo "<ul class=\"member-list\">"; foreach($members as $member) { echo "<li class=\"member-item\"><div class=\"member-name\">{$member->last_name}, {$member->first_name}</div><div class=\"member-address\">{$member->street_number} {$member->street}</div></li>"; } echo "</ul>"; echo $paginate; ?> </div><!-- end member-directory --> </div><!-- end container --> <?php include("./foot.inc"); ?> Has anyone encountered anything similar to this? Is there something in the selector that should change or something missing from the selector? Any help would be appreciated. The site is live and I thought it was working until someone pointed this out. I'm not sure if something changed to cause it or if I just didn't notice.
  8. digitex

    No the last names are all uppercase. Members were imported from CSV and they were like that on import. It's good to know though. I switched the selector to title instead of last_name and it sorted properly. The only difference I can see between the 2 fields is title is lowercase so I wrote a function to convert all the last_name values to title case and it seems to be working now. I still think it's odd behaviour that uppercase should have sorting issues. Thanks to Zoeck for the insight.
  9. digitex

    That's the first thing I checked. I even cleared the field and re-entered the names manually. That's not it.
  10. I have a list of users that I want to output in a paginated directory in alphabetical order by last_name. When I first wrote it, my selector looked like this: $members = $pages->find("template=user, roles=member, limit=100"); it sorted correctly as follows: AGLA, H AL, J AL, L BAILEY, M So then I added a sort to ensure it lists by last_name: $members = $pages->find("template=user, roles=member, limit=100, sort=last_name"); The resulting order looks like this: HALLS, T WEBSTER, T AGLA, H AL, J AL, L BAILEY, M The obvious question is why is Halls and Webster coming before Agla? Can anyone explain it for me? I want to add a filter to allow sorting A-Z and Z-A so I need to include a sort in the selector but I need to get it to sort correctly first.
  11. Thanks @dragan. The hooks in that link are the correct way to do what I want and I will read up on it. It's better than changing the code in the module I think.
  12. Hi Guys, I'm hoping to get some suggestions. I'm using Pollino on a site and it's working great, thanks to Soma and BitPoet (I'm using his version for this project). The boss wants to prevent voters from seeing results after they vote. The site is for a home owners association and only logged in members can vote but the president of the association wants to be able to use the poll results to present to municipal council as official feedback on local issues so he wants to be able to present the results of each poll himself, after the voting period expires. I'm hoping a simple conditional can be used to only present results to the admin role and just a thank you for voting to members but I can't seem to make it work. Can someone who has dived deeper into the code than I help me with a place to start?
  13. digitex

    @adrian I suspect you're right that it may be a specific issue with Ryan's module. With Login/Register/Profile the profile page is the same as the log in page and the profile UI is loaded with a GET variable. It may be the get variable in the Frontend Login URL that's causing the error. When logging in using a member's credentials it does try to redirect to the profile page but throws an error when it gets there. As for the superuser role getting the password change notice I will have to get back to you. When I get a minute I'll reinstall and enable debug. I would love to use it I'm importing 250 user accounts and need to ensure everybody updates their password.
  14. digitex

    I had to uninstall this one. Is it compatible with pw 3.0.96? Once installed I set the frontend login URL for profile edit to the correct frontend page (/member-login/?profile=1 using Ryan's Login/Register/Profile module) and I get an Internal error. Won't load the page. Additionally I set it to force all users with the "member" role to change password and as a superuser I get the message to change my password. I don't have the member role. When I set it to clear superuser, on next login I get the same message to change my password.
  15. digitex

    I went and had a shower, great place to think. I found a solution that doesn't require hooks. It's a simple CSS thing. For anyone in future thinking of using flex-box for the edit profile form, which does look and work better than floats, you can try this: The Inputfields class is common for all of the forms in the module and is where flex needs to be applied but the forms themselves have individual IDs which allows you to target the .Inputfields class as follows: .Inputfields { display: flex; } #LoginRegisterProfileForm > .Inputfields { flex-direction: row; justify-content: space-between; align-items: stretch; flex-wrap: wrap; } #LoginRegisterLoginForm > .Inputfields, #InputfieldForm1 > .Inputfields { flex-direction: column; justify-content: center; align-items: stretch; flex-wrap: nowrap; } #wrap_login_name, #wrap_login_pass, #wrap_username { display: block; max-width: 50%; margin: 0 auto 10px auto; } If that's helpful to anyone.