Jump to content

digitex

Members
  • Content Count

    201
  • 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,968 profile views
  1. I didn't even think of that. Thank you.
  2. I'm working on a site that's using a background video on the home page. I've run into a problem though. I created a file field to hold the video and call it in with the following: <video class="video-background" loop no-controls autoplay src="<?php echo $hp->video->url;?>" poster=""></video> This doesn't work and throws this error: HTTP load failed with status 403. BUT when I upload the video to a sub-directory in Templates and use this code: <video class="video-background" loop no-controls autoplay src="<?php echo $config->urls->templates?>css/images/WB5.m4v" poster=""></video> It works. I expect it's an htaccess thing but I can't understand why since any other file works fine why is video different and what do I need to do to get around it?
  3. It happened only on that page in that spot and didn't change when I turned the h4 into an h3. I found nothing in the CSS or any JS that would effect it. It seems the browser(s) were rendering that area as if it was inline. I'll try @OrganizedFellow's suggestion. Stupid gremlins.
  4. My understanding has always been that block level elements get 100% width by default. Has that changed? I have fixed the issue by writing a CSS rule to govern <p> tags setting the width to 100% but I've never had to do that before. Shouldn't have to do that. Still have no idea why that's displaying that way without the new rule. Freaked me out but I have it under control again. So it's solved (ish).
  5. Help! I'm working on a privacy policy page. The text was submitted as Word so I first pasted into BBEdit to remove the Word formatting then pasted into CKEditor on the site. In one spot only an H4 tag is displaying inline somehow beside the previous paragraph instead of on it's own line. See the heading "ACCURACY" below. I searched for hidden characters using 3 different text editors and an online service, I checked it in 3 different browsers. There's no code that would target that and no JS or CSS effecting it. It displays correctly in CKEditor: And when you look at the source markup there is nothing that would cause it: The last paragraph of text is a single line and the only way I can fix it is to insert additional text to force that paragraph onto 2 lines: Has anyone seen this before? Is there something I'm missing? I'm going nuts and can't spend the rest of my life on this. Any help is appreciated.
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. That's the first thing I checked. I even cleared the field and re-entered the names manually. That's not it.
  15. 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.
×
×
  • Create New...