• Content count

  • Joined

  • Last visited

  • Days Won


clsource last won the day on January 21 2017

clsource had the most liked content!

Community Reputation

561 Excellent

About clsource

  • Rank
    Sr. Member
  • Birthday 10/18/1989

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

6,217 profile views
  1. The Authorization Header is eaten up by Apache in some configurations, for avoiding that is recommended that you send another header like X-Auth-Token with the same info "Authorization": "Bearer API_KEY" "X-Auth-Token": "Bearer API_KEY" Then you just check if the auth is empty then fetch the other header as a fallback. Hope it helps
  2. Hello, maybe you could be interested in this post Basically the JAMStack is just a Website with JS and a REST or GraphQL API. Wich can be easily done with PW if you need to. A JAMStack is not needed for every project though
  3. Not really at the moment. Just an idea JWT is just a communication system. If you look at the profile is the Processwire auth system that is used at the end. Instead of using oAuth or Basic Authentication JWT can be used for getting user roles and data without requiring to log in the user on every request, saving server resources
  4. Seems great. Awesome Job!. Thanks for sharing. I think the JWT Auth may become a module on it´s own. For folks who don´t know about JWT. It´s a standard for Authentication Using Json.
  5. I think comparing PW to Django is like comparing PW to Laravel. They are different beasts with different use cases. All of them are Awesome (Althought I prefer Flask, Yarrrg for pirates!) Maybe comparing PW to or could be more fair since they are CMS just like PW is. I think the bottom line of chosing a toolbox is down to simple questions: 1- I like using it? 2- What use cases can I fulfill? 3- Makes my team and clients happy to work with? So just use what is best for the requirements, restrictions and overal context of the project at hand. Not all projects can be done with Laravel, Django or PW. Maybe you can mix both and have the best of them :).
  6. That's a totally valid point. I should see elixir so I can move away from Laravel to create rest apis and systems. The only benefit of Laravel (And other PHP Frameworks) is they can interact with the ProcessWire API directly (Using composer and namespaces). But that can easily be solved with a simple Rest APi although requires more work
  7. Hello, Upon reading these articles I was thinking that PW can be used for a Jamstack or Headless CMS with no changes at all. You can easily create REST Api with PW or use the GraphQL module So ProcessWire is an Open Source Headless CMS since 2010
  8. Technically PW Admin uses the API available. It's just a front end. So if someone wants to create a totally new admin front end that uses some js libs like It's totally possible. But keep in mind that many third party modules depends on jQuery. So if this is implemented in the core it should be ProcessWire 4 or something indicating a huge change.
  9. Hello and welcome to the forums. You arrived at the right place we are a friendly community happy to help newcomers. About your question: Yes, but as the agency said. It should be configured to do so. Wordpress does not have this functionality either. every wordpress theme comes with their own settings and options. So the agency programmed your site but it didn't program Processwire to include such settings. Maybe wasn't in the original specs. As you mention that you know html and css it seems that you have all the required knowledge to integrate this feature in your site. Just go to the templates folder and take a look for the files. You will encounter many files with html in them. One of them will have the <head></head> tags and you could change the fonts easily
  10. I use VS Code often, but PHP support is far from good compared to other editors like Sublime Text. VS Code is great for Javascript though.
  11. Thanks for your reply As a matter of fact. I was tasked in creating a form heavy application. I started using NativeScript but the designers abused the combo box (html select option) in the desings. Because picker views (combo box) were huge in the native implementation compared to the web versions, the UX should be redesigned from scratch (there were so many inputs in the form that a single screen should be separated in 5 or more just to be more simple to use). So because time and money constraints the solution was: throw away Nativescript and just use a web view with onsen framework. Onsen, Nativescript, Jasonette or React Native are wonderful tools for making Apps with Javascript. It's important to know the limitations and capabilities of each tool and select the right one for the job at hand.
  12. NativeScript is great too. But keep in mind that if you need an app that is form heavy (like many apps for enterprises) just using html forms maybe the best choice. The problem with NativeScript and other "Native" frameworks is the UX needs to be tailored for native style apps. If you only have developers and designers experienced in the web UX you will have troubles adapting the web UX to the native UX.
  13. Hello, I just want to point out this framework for making html apps it's compatible with jquery, angular, vue, react or any other js framework. So far I made an app using this and bootstrap with for the desing and some libs like jquery and lodash for the app logic I prefer this to other alternatives like ionic since it does not bound you to angular or react. Cheers
  14. Awesome job!. Seems this could become very handy when making projects for clients.
  15. Maybe this could be used too