Jump to content

netcarver

PW-Moderators
  • Posts

    2,137
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by netcarver

  1. The v2.5.1 version of textile just gained better support for responsive layouts by optionally omitting dimensions from images. I'll have to work out how to make the TextileTextformatter modules configurable before I can add a control into the module for this feature. I'm beginning to think that I might just make omitting the dimensions the default in PW for now.
  2. Hi vanni & welcome to the PW forum. Yes, that's correct, in PW the equivalent of TxP forms & pages are file based so you get to edit them with the editor of your choice and/or version control them all. There are differences in terminology between PW and TxP too and "template" is one of them. Attached is an image that might help explain some of the PW terminology (with props to SiNNuT for the starter idea.) If I remember correctly, there is also a module for PW that allows you to edit your template files via the admin interface but I haven't used this myself and I may have that wrong. Another major difference between TxP and PW is that PW uses PHP as the template file language whilst TxP has its own tag system that it has to parse. Hope that whets your appetite a little and that you enjoy trying out PW.
  3. Just updated these formatters for textile v2.5.1 which was released about an hour ago. HNY!
  4. Here's the box on my "desk"*. Still hanging in there. * Actually a salvaged door.
  5. netcarver

    Amazon API

    Hi Pete, Interesting to hear about your use/planned use of one of the Amazon data feeds & PW. I run a little shop listing about 50k items on Amazon at present, some custom coding but mainly using a commercial, closed source, product that I'm now working on replacing as it is too inflexible & expensive for our processes. I've been looking at libraries for the replacement work and found another link you might want to consider if you have pro-merchant account access; this fork of guzzle-aws includes an implementation of Amazon's MWS API. If you don't have a pro merchant account, sticking with the product advertising API feed is free. BTW, the link I've included is for source code that is driving a live shop and seems to have very recent activity. I'm just about to start using it. If you do store data locally just be aware that the terms of service for the APIs have a max cache-time clause to keep price info fresh (24 hours max IIRC.)
  6. Were those results obtained over an internet connection, your local lan, or testing on localhost? I did some benchmarking of my own a while back and as part of that I benchmarked static file serving times on Apache2 and nginx. I was getting times in the order of 56μs per read from Apache2 and far less on nginx but that wasn't over the internet. FWIW, here are some apachebench results for default installs of PW on Apache2... ...the "failed attempts" are false-positives as the default site homepage has a random image. (Apachebench assumes all reads will lead to the same sized data and flags all following reads that return different size pages as "failed requests".)
  7. netcarver

    Hi Everyone

    Hello kongondo & welcome to the PW forum. Whilst I agree that Ryan's produced an amazing product in ProcessWire I think it goes beyond just the software. Of the CMS devs I've been involved with Ryan's the one project lead who has been the most open, from first contact, to meaningful contributions towards the site, docs, forum and code. Some others have been open, most friendly, but none to the same degree. Consequently he's attracted a welcoming, talented & professional group of people to the project and I've learned a lot from being involved here.
  8. Hello DDV and welcome to the PW forums. As far as I know, 1902 is the earliest date you can represent on any 32-bit unix-like system that uses "unix time" to represent dates. This is not a limitation with ProcessWire per-se but because the time data is stored in "unix time" which is an integer representing the number of seconds before (negative) or after (positive) the "unix epoch" which is 01-01-1970. This allows +/- 68 years around the epoch year, meaning the earliest year you can represent is 1902. More information about this issue on Wikipedia (esp. the section on "Representing the number"). If you do not need to perform any manipulation of dates, you could just keep them as strings.
  9. Looks like Packt Publishing have another ebook offer on, valid until the 3rd January. All their e-books are US$5(£3) each but you have to buy a minimum of two for this to work.
  10. @moreweb any chance you could put that code in a gist over on github, or on paste-bin or something? Removing the leading whitespace will also make it more readable. I can't make head nor tail of it on the forum
  11. Hmm, 22 chars is what ircmaxell's PHP5.5 compatibility library uses for bcrypt salts.
  12. @Neil Darlow Welcome to the ProcessWire forums and, wow, what a start! Thank you for sharing your production config file, that will save me (at least) some research.
  13. Update: new versions (v2.5.0 and v3.5.0) now available. Yes, two versions. Both are feature compatible (at least they are at the moment) but differ in that v2.5.0 is not PSR-0 compatible as it doesn't use PHP5.3's namespace facilities. v2.5.0 only needs PHP5+ and is therefore suitable for projects targeting older versions of PHP. v3.5.0 is PSR-0/1/2 compliant and needs PHP5.3+ for namespace support. @Ryan, I'll be in touch soon about taking over maintenance of the Textile text-formatting modules for PW.
  14. Hi Michal, I kind of agree with Pete. Basically, if someone can do an SQL injection via the application, they could just inject the "show tables" SQL and get all the names then target specific tables.
  15. @Nico, sure thing. Thanks for becoming a module mod
  16. Perhaps some kind of gallery for admin themes & predefined profiles?
  17. Hi Harm, Basically, I think it's that trailing "|" that is the problem. Try building your $teams variable like this... $teams = implode( "|", $user->teams); This is untested but might work. If it doesn't then just change the way you build the $teams variable slightly... foreach($user->teams as $team) { $teams .= $team."|"; } $teams = rtrim("|", $teams); // pop off that last "|" Hope that helps.
  18. netcarver

    PGP Encryption

    Sorry, I don't use either Hani, but if you don't get any help here then I've often found IRC channels to be quite a good way of getting help. There are some channels for these topics on irc.freenode.net and #gnupg looks like the best bet judging by the names. You can join the channel via webchat in your browser too. Hope that helps.
  19. Fulltext stopwords might have something to do with it too -- but I've never used fulltext indexes so I'm not very familiar with them at the moment.
  20. Just a quick update. I've now pushed a preview of the changed code to a new 'nr' (next-release) branch. Feel free to post comments, suggestions or questions here or raise issues over on the repo itself. I've actually started documenting the methods too -- something that will be ongoing over the next few point releases.
  21. @Mathew Thank you for the report, I appreciate it! Actually, TextileRestricted() intentionally does not convert these structures to lists. It's restrictive as it's meant to be used for things like public facing inputs like comments which can easily be abused. As you've found out already, you need to use the normal unrestricted textile if you want lists rendered properly. As a slight aside for a moment: You mentioned using... *Publications* * Publication 1 * Publication 2 ...as the input but this version of textile requires a newline between what you are using as a heading and the first item in the list, like this... *Publications* * Publication 1 * Publication 2 Ok, back to the main thrust. If this isn't a public facing application and you need to have users input lists then you could consider switching over to the un-restricted formatter. If you do need restricted mode (untrusted users) plus lists then please raise an issue over on the repo and I'll see what I can do. I'm not particularly happy with this split between functionality between the two textile methods at present although it seems to have done what most people need until now. I have been thinking of adding a more general and flexible parse method to which you can specify exactly what structures should be allowed, but that's just a thought at the moment. Thank you for your interest in textile.
×
×
  • Create New...