Jump to content

SiNNuT

PW-Moderators
  • Posts

    1,011
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by SiNNuT

  1. Ryan, this, and the whole of PW just reeks of awesomeness! Unfortunately i'm not in a position where i can promote PW in way that would actually matter, so you better set something up so we can contribute in a monetary fashion. You deserve some Euro's coming your way for the pleasure i've had working with PW.
  2. +1 for Sublime Text 2. Been using it a couple of weeks now and i'm a fan. Will probably buy a license.
  3. Thx Soma. I searched the forums but did not think of the stopwords. Sometimes it's hard to remember if stuff has been asked before What added to my confusion was that i wasn't able to find any 3-letter page titles with the default selector. Ofcourse, it's in the docs. I sometimes forget a lot of info is already there. Regarding the Site Map example using ~= : Here it also encounters the lenght stuff i guess. It seems to treat every word on it's own if there are spaces. Rename Site Map(3 characters) to Site Mapp and it finds it perfectly well with ~=.
  4. I guess you guys are right. Was looking to much into the 'correctness' of things.
  5. I'm trying to build some sort of 'frontend' administration area where users with the right roles can add and edit certain pages. So basically a CRUD area (minus the D in my case). I don't want to give those users access to the PW admin. I have created a template which manages accesss, children of a page using this template will inherit access from this. First thing i did was to remove the guest role from roles that can access pages using the template. Visiting the pages on the frontend as guest results in 404. This is expected, because that is the setting i chose for: If a user attempts to access a page using this template, and doesn't have access to the page, what should it do? In the ProcessPageView.module a 404 header is set. Wouldn't it be appropriate to throw a '401 Unauthorized' response code? 404 is often used as catchall but in reality is not for resources that do exist. So basically the addition of a Wire401Exception? We could have a 401 page in addition to the 404 page currently in a fresh PW installation. Any thoughts?
  6. Before i report a bug on Github i want to ask if there are more people that are experiencing problems with the search feature in the admin. Scenario: A fresh install of PW. Search for 'templates'-> Found 1 page using selector: title~=templates Search for 'about'-> Found 0 pages using selector: title~=about Search for 'about'-> Found 1 page using selector: title=about Search for 'site map'-> Found 0 pages using selector: title~=site map Search for 'site map'-> Found 1 page using selector: title=site map Search for 'site'->Found 1 page using selector: title~=site (the page with title "Site Map") Maybe i'm confused about the different types of search but if the templates page is found, the about page should also be found? Also the above sitemap search doesn't seem logical in result.
  7. Probably the 'easiest' and most effective way to deal with high traffic websites is using a caching HTTP reverse proxy, such as Varnish cache or squid cache. It sits in front of your web-stack and caches and serves cached versions to your visitors, greatly reducing server load. See for example http://highscalability.com/blog/2011/2/28/a-practical-guide-to-varnish-why-varnish-matters.html Of course, this doesn't apply to cheap shared hosting.
  8. nikola, maybe something like this?
  9. Will do whenever possible.
  10. The README contents in the topicstart are outdated. I've added Dutch country names to the list. For future reference check out the github page because i'm not gonna keep the topicstart up to date. @Pete I also love the icondrawer flags but there are some restrictions to it's use if you honor their wishes (i.e. put a link on a site) The other flags i mentioned are pretty neat as well and are unrestricted as far as i can tell.
  11. I agree with Teppo. It's really quick and painless to create an account on MediaWiki so why not make this a requirement for contributing to the wiki. For the most part this will do away with spam.
  12. Nice site Orkan. Good use of bootstrap as well; bootstrap is nice but a lot of sites that use it look too 'bootstrappy' You've managed to avoid that imo.
  13. It seems like something fishy is going on on wiki.processwire.com? Maybe we should take some precautions for this kind of anonymous shit?
  14. I'm not sure but couldn't this has got something to do with using non-strict comparison on objects and circular references? http://www.richardlord.net/blog/php-nesting-level-too-deep-recursive-dependency http://stackoverflow.com/questions/8460011/in-array-on-objects-with-circular-references
  15. - Not sure where to post this- I just made a country list and i thought it might be useful to someone so i put it on github. You could use this for example with the importpagescsv module to easily create country pages for use in your site, forms etc. For now it's English only ( i could add other languages if someone needed it) README.md About This is a complete ISO 3166-1 encoding list. It is listed in alphabetical order by the English short country name used by the ISO 3166/MA. There are currently 249 ISO 3166-1 countries. England, Northern-Ireland, Scotland and Wales are added to that because they are used by FIFA. It also contains the corresponding IOC and FIFA three letter codes and the filenames of the country flag image(s). Total countries: 253 Fileformat: txt file separated bij tabs Data is taken from: http://en.wikipedia....wiki/ISO_3166-1 and http://en.wikipedia....6_country_codes Flag icons I included the flag icons from http://icondrawer.com/free.php See the link for details and terms of use. You can also get the flags in a wide range of sizes and flavors from this awesome project: https://github.com/koppi/iso-country-flags-svg-collection For the least amount of hassle: https://github.com/koppi/iso-country-flags-svg-collection#download-the-icon-sets
  16. I think that would be a great idea.
  17. SiNNuT

    DRY URLs

    I think Ryan's suggestion will work. Question alan: how will you know that an external link has changed?
  18. SiNNuT

    DRY URLs

    Hi Alan, look at this post from Ryan for 2.3. features. I can also remember Ryan saying something about using links in Tinymce fiels and the like that they where going to resolve the page id or something like that. - edit - found it Your idea, to me, doesn't seem that 'DRY'?
  19. Just as a little side note, i quite like the way the laravel framework presents their 'bundles' section. Of course, this could be modules as well. http://bundles.laravel.com/bundles/'>http://bundles.laravel.com/bundles/ http://bundles.laravel.com/
  20. Everyone thx for the responses. It's quite interesting to see what i can come up with in PW. You have to structure your data well and on the other hand it has to be as easy as possible from a data entry/UI point of view. @arjen This is indeed an interesting question. I'm having a look at other sites how they approach this. Examples are http://www.cqranking...r.asp?riderid=7 and http://www.cyclingnews.com/teams/2012. They seem to take an approach where they have a Team(code) and for every calendar year they list the riders. On a Rider page you can see their current team and past teams. If he's not associated to a team in the current year i guess they are considered inactive. So i'm thinking about doing the Riders and Team like this, where every rider is a page and from every year page of a team link to the riders via a page field. Teams: Riders: Team A Bradley Wiggins -2013 | -2012----| -2011 | Team B | -2013 | -2012 | -2011----| Now to manage participants for a Race it's not as simple to just link to a certain team-year page. This is because a team can have for example 15 riders and only 6 are allowed to enter the race. I'm not sure i will be able to pull this off completely because my coding skills aren't really up to par but it sure is fun fooling around with it.
  21. I'm working on a site redesign and migration from MODx to PW for a foundation that organizes cycling races. The site itself is fairly simple and the content not that much. Talking about the site we figured it would be pretty neat if there was an easy way for us to manage the cyclingraces and its participants from the PW back-end. Some numbers: - For now it's two to four Races a year but this could grow - A typical Race is ridden in Teams. Dependend on the type of Race Teams consist of 3 or 6 Riders. There usually are between 25 and 40 Teams and between 120 and 180 Riders. - Participating Teams are numbered (1,2,3..) each rider gets a startnumber (1-6, 7-12, 13-18..) At any given time a Rider belongs to one team, but ofcourse can belong to many over the course of the years. Sometime before the race teammanagers start to email or even snailmail provisionary lineups. So the typical use is this (via PW backend): A foundation member adds a Race and all it's info. He can also add the participating teams with their corresponding line-ups. On the front-end all of this info is displayed and up to date. Later on it would be really nice if a team manager could login to a page on the frontend where they can manage their line-up themselves. Simplified, and maybe not correct at some points, this would look something like this in a more traditional db schema (see pic below) I thought about adding Teams as children of a Race and the Riders as repeaters but although this works quite nicely from a ui perspective this isn't the way to go. I not looking for a definitive answer but if someone could give some tips or thoughts on how they would approach this it would be great.
  22. As a bit of a MediaWiki learning experience i've put the project walktrough on the wiki. Not sure if this is the place where it ultimately resides, but anyways. http://wiki.processwire.com/index.php/Small_Project_Walktrough The wiki could do with a bit of syntax highlighting. http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi Maybe later on i can actually contribute to the actual content of the tut.
  23. Ah, totally forgot about the wiki. I agree, that would be a great place to add some quality stuff. As mentioned above; a great start would be to finish the project walk-through. It's already a nice intro, adding some stuff about page relations (page fieldtype) to efficiently manage your content and possibly url segments would be great. I'll see if there is anyway that i can contribute.
  24. I'm not sure that this has been posted here before but via Twitter i stumbled upon this site: The Unofficial ProcessWire Docs I also like the post that explains why this site was made. Making, maintaining and updating great docs is hard work and requires a lot of effort. The api docs on processwire.com are a good start but i agree with what is said in aforementioned blogpost. The unofficial docs site seems like a nice addition to the PW community; a place with nice how-to's, useful tips, plug-in docs, etc. It already seems populated with some pretty interesting stuff (especially for those of us who aren't already PW guru's) I would encourage everyone to visit the site and possibly start contributing.
  25. Great looking site and nice video about how it works. If i where a photoshop user i would definitely buy it! BTW, is that slash character your own creation? Having zero design skills i'm always in awe of stuff like that. You use illustrator for such things?
×
×
  • Create New...