benbyf

Admin doesn't really function without js

Recommended Posts

PW Admin doesn't really function without javascript, and my question would be, should we care?

I think, however, either way it might be nice to add a "<span>Javascript doesn't seem to be available, therefore you may not be able to access the full functionality of the admin</span>" somewhere maybe?

  • Like 1

Share this post


Link to post
Share on other sites

pw needs javascript all over in the admin so there's no way to make it work without.

i agree it would be nice to add a warning. the login screen would be a nice place. you could do a PR and add some warning here that would be hidden via javascript and therefore only visible to clients without javascript.

https://github.com/processwire/processwire/blob/master/wire/modules/Process/ProcessLogin/ProcessLogin.module#L427-L451

  • Like 2

Share this post


Link to post
Share on other sites
8 hours ago, benbyf said:

PW Admin doesn't really function without javascript, and my question would be, should we care?

I would say that it's been many years since developers had to worry about a site not working without JS. Back in the early 2000's it was considered evil and we did all sorts of things to avoid using it (and to make sure we used graceful degradation techniques), but these days there aren't many sites that you can use without it even on the frontend, so expecting it for the backend of a site shouldn't be an issue at all anymore. 

Facebook does this:

59c3b663b8ae9_ScreenShot2017-09-21at5_53_11AM.png.529bd552a274f7d5ba9be80ab57af117.png

but you guys should take a look at the old "m.facebook.com" site with javascript disabled - it looks ancient :)

  • Like 3

Share this post


Link to post
Share on other sites

i totally agree. i don't think it's necessary, but i think it would be nice to have a warning on the login site. a simple noscript tag could make things clear and save us from support-requests like "hey, my admin tree does not show up" where one's first thought could be a permission problem or the like...

  • Like 5

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By pwuser1
      Hi does anybody know of any editor that supports our great PW?  Paid or free is fine.
    • By pwuser1
      Hi does anybody have experience in converting Wordpress Themes into Processwire Themes?  There must a more efficient way than my cut and paste and check...
    • By nickngqs
      How do I change the permissions for Who can access this page for a single page.

      This page inherits the admin template.

      I'm currently creating a new page called Settings using admin template and assigning it to a process of a module. I can see the Settings tab in superuser, but I can't see them in a role I defined called 'client'.

      So, how can i control what the client sees for admin template? Is there a page specific overwrites for permissions. I've tried allowing access in admin template view, edit. But still doesn't work
    • By Nukro
      Hi Guys
      It would be awesome when all the resource about processwire (tutorials, docs, cheatsheet, recipes, videos, api, faq etc...) would be unified on one documentation website called "docs.processwire.com".
      The new site would gather infos & data from these resources:
      https://processwire-recipes.com/ http://processwire.tv/ https://www.pwtuts.com/ https://processwire.com/docs/ http://cheatsheet.processwire.com/ and would unified it on the final site https://docs.processwire.com.
      I think It is far more better to have one endpoint for all the processwire resources & wisdom then mutliple sites. This way it is far more easier to get into the processwire world and choosing processwire as the next main cms for further projects.
       
      The Documentation Site could perhaps look like this (it is just a mockup, so don't expect to much from me ):