Jump to content

Craig A Rodway

  • Content Count

  • Joined

  • Last visited

  • Days Won


Craig A Rodway last won the day on January 4 2016

Craig A Rodway had the most liked content!

Community Reputation

546 Excellent

About Craig A Rodway

  • Rank
    Distinguished Member

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location
    Gateshead, UK

Recent Profile Visitors

9,367 profile views
  1. I think this is a great addition! I made something similar a while ago (called Widgets) but it wasn't as thorough, simple, or effective as your Component implementation. I look forward to trying it out πŸ™‚
  2. I've been working with CodeIgniter for over 10 years, and although the general framework structure is predictable and documented, the custom code and database layout that has been developed with it could be... anything! You don't really have to learn it, but being aware of how it works might be useful in extracting the bits you need. I think these two documentation pages will be most helpful at this stage: https://codeigniter.com/user_guide/overview/appflow.html https://codeigniter.com/user_guide/overview/mvc.html As a rough guide, the URL patterns (/foo/bar) of a CodeIgniter app usually map directly to controllers. These should be in the application/controllers directory, and each file in here is a class. The example URL route of /foo/bar would call the bar() function in the Foo.php controller. Within the controller, it should (might!) call some 'models' - responsible for database interaction - and pass the result data into the 'views'. The views are responsible for transforming the data and results into HTML code that is sent to the browser, so this is likely where the main page layout should be, along with the different code for producing the different lists and detail pages. These live in the application/views folder. By default, there's no templating language or library used (like Twig) - the views are just mixed HTML and PHP, like ProcessWire, so should hopefuly be easy enough to follow. In terms of the database, you will need to look at how the current one is set up. With any luck, you could probably map each database table (books, movies, events) into PW templates of the same name, and set up PW fields that correspond to the columns in the database tables. After that, you would need to address any relationships or links between the tables or records, and decide on which PW structure will be best. For example, parent/child pages, Page reference fields, or creating a tagging/categories setup. If there's any budget for the project, I have some time over the coming weeks and would be happy to help you in the right direction if you think it would be useful πŸ™‚ Craig.
  3. @ryan Just submitted a site to the showcase on the new site, and the redirection took me to /sites/thanks/ - but this shows a 404 at the moment. πŸ™‚
  4. Hi all! Happy New Year πŸ™‚ I recently rebuilt the website for classroombookings - my open-source room booking system for schools - using PW πŸ™‚ classroombookings.com I started the project itself way back in about 2006, when I was working in a school and needed a solution. Over the years I haven't made that many changes to it - mostly due to lack of time - but it has a modest userbase. Fast-forward to late 2018 when it required a major update to support PHP 7, fix some issues, and I also launch a hosted service. The website serves marketing, documentation and download/release functions for the project and I think PW is ideal for it. In the spirit of open source, the code for the website is also available on GitHub for anyone who wants to poke around and see my approach to PW web builds. The site is pretty standard, the only 'custom' bit is the releases section, which it pulls from GitHub using their API and creates/updates pages (Releases module). The frontend uses the Spectre CSS framework, and this is the first site I've built using it. Modules: AdminTemplateColumns ProcessDateArchiver SettingsFactory TextformatterHannaCode
  5. Looks brilliant πŸ™‚ Win 10 Firefox - whole page screenshot. The only thing off is the Docs menu is still opening to the right and appearing off-canvas as mentioned elsewhere in the thread.
  6. Ha πŸ™‚ Being a Windows user, I get Segoe UI when it's used, and I quite like it and prefer it over Arial. I have noticed some slight vertical alignment things but it doesn't bother me that much.
  7. Have you thought about not using any webfonts at all, and instead use the native or system CSS font stack? Doing this removes any cross-browser/device font rendering issues as well as removing several external resources (smaller download + even faster loading!) There seems to be a shift towards this: https://booking.design/implementing-system-fonts-on-booking-com-a-lesson-learned-bdc984df627f http://markdotto.com/2018/02/07/github-system-fonts/ https://make.wordpress.org/core/2016/07/07/native-fonts-in-4-6/ Other resources: https://woorkup.com/system-font/ https://css-tricks.com/snippets/css/system-font-stack/
  8. I saved a copy at the time - here they are (I think!) πŸ™‚
  9. I would say Stripe is a leader in this area and a good option to consider. Failing that, there's always PayPal
  10. When I've needed to implement a multi-page process, I've stored the user's responses in the session, using the built-in ProcessWire Session handling code. If anything needs to be permanent at the end of the process, only then would I create the necessary pages.
  11. You need to call this as a function to get all POST data: $input->post();
  12. I've done an implementation of "magic link" logins via email on a previous (non-PW) site using HMAC SHA1 to avoid having to store passwords. On an upcoming site, I plan to do a similar thing but using JWTs to encode and verify the data, as it's a better standard than just concatenating a bunch of values
  13. You can double-click the bin icon on file/image fields to mark all items for deletion.
  14. I recently experienced a similar effect too, across three sites on two very similar servers. Running 5 requests with no caching against the PW Admin login page, as guest, these results are the median response time for just the page request: Server 1, PHP 5.6.15, Site A, PW 2.7.3: 217ms Server 2, PHP 5.6.22, Site B, PW 2.7.1: 293ms Server 2, PHP 5.6.22, Site C, PW 3.0.17: 672ms I noticed the slower time when Site C was first launched, but had little time to really investigate it there and then, and haven't got round to it since.
  • Create New...