Mike Rockett

Members
  • Content count

    1,278
  • Joined

  • Last visited

  • Days Won

    8

Mike Rockett last won the day on October 22

Mike Rockett had the most liked content!

Community Reputation

1,053 Excellent

About Mike Rockett

  • Rank
    Hero Member
  • Birthday 03/07/1991

Profile Information

  • Gender
    Male
  1. Not sure how that’s possible, but it could be related to caching. If you provide more information about your setup and what jumplinks you have created, I might be able to assist. It’s on ice at the moment due to new work that’s come in. Time is super limited until earlyish next year, at which point I can revisit v2. Sorry for the delays, but it’s unavoidable at the moment.
  2. @adrian Thanks, will patch and test it out in a few hours… Time to do system updates now (in desperate need of Windows subsystem for Linux).
  3. Not sure if this is due to any changes in this specific version, but I’m not able to upload images (tested in a user profile). It returns with Invalid POST Data. Upon further investigation, it seems to come from this: /wire/modules/Process/ProcessProfile/ProcessProfile.module (line 213) When uploading the image, it sends a post request to /admin/profile/?InputfieldFileAjax=1, with the following headers: X-FIELDNAME:image X-FILENAME:6.png X-REQUESTED-WITH:XMLHttpRequest The user ID doesn’t appear to be set in the request, which is why the error is thrown. Interestingly, the HTTP code returned is 200… After that request, another is made to blob:http://domain.lserv/aa5ddd22-6dbf-42e0-9d12-1cee83b8fb39, which returns the image I uploaded, yet it does not exist in the files directory. (Honestly, I don’t know how AJAX uploads work behind the scenes, so this part of it could well be by design…) Is there something further I need to do, or is this a geniune bug that needs reporting?
  4. I just noticed that it’s not possible to turn off email notifications for private messages. The tooltip for the relevant toggle-switch says that an administrator has disabled it. @Pete, would you mind re-enabling it? I sign into the forums every day, and so an email notification of a private message is practically redundant.
  5. Thanks, figured as much. Will need to rework this on the front end then.
  6. The current generator uses an array for “permission”, which doesn’t seem right as the API docs state it needs to be a string… Which is correct? Also, if a permission is created via the “permissions” array, surely they would all need to be in “permission” as an array as well? This how I’m doing it in Jumplinks, anyway (hope I’m not wrong). Or perhaps “permissionMethod” should be used for multiple permissions? Some insight would be appreciated.
  7. A little while ago, I began a complete rewrite of the module that was set to add additional features (like SASS and Stylus, for example). Unfortunately, I won’t have time to work on it as fast as I’d like. But, it’s still something I’d like to do.
  8. @Pixrael I hear ya, though inline styles is not something one should implement in their own HTML, but allow the framework to handle it for you.
  9. I see the points being made here. @BitPoet, you're quite right -- didn't think about the jsonification of things. That could surely be implemented, but it brings us back to the question of purpose etc. Truthfully, doing this would be quite a mammoth task, considering all the aspects involved. @titanium Well, I think age may have been a bad choice of word... I look at the updates, and it's been seemingly quiet (except for master branch, which has activity). @szabesz Sure, understandable, though my thinking is more about what the newer frameworks are capable of, and less about their cool-kid-on-the-block status, which has never been something I think much about. Sure, it pops into the mind, "that's really cool" -- but jQuery was the same when it launched, and then sky-rocketed. I can agree with a jQuery version bump at the very least... Someday, PW's default interface and experience could well be powered by a fully fledged MV* framework, and I'm convinced that it's quite fitting, considering that it's not a simple app at all.
  10. @teppo I do have to agree - one would need to determine what what purpose it would have and, yes, how much sense it would make. In my view, I think front-end frameworks bring a lot to the table, and that they could indeed enhance the experience. Having known jQuery for a long time, I'd be inclined to make this a slow process, if it were up to me. For my own projects, I'm no longer using jQuery for a multitude of reasons, one of which is its age (and not necessarily because all the cool kids are doing it). Given that the PW admin has multiple aspects to it, and that it could well be considered an 'app' from that perspective, I think a front end framework could fit in well. Sure, there are a whole bunch of other things to consider, like modules needing jQuery, but there's nothing wrong with that, and PW could just load it in when the first module in the queue asks for it. I would really like to see the PW admin become a single page app.
  11. Absolutely -- totally possible, and that's just what I was thinking about the other day. Definitely.
  12. My belief has always been this: if there's a tool available, use it. PW would greatly benefit from a reactive / flux-based (Vuex) way of doing things. If the backend were a complete SPA, that would be absolutely magical!
  13. Interesting you bring this up -- was thinking about it the other day. Would love to see this happen, especially in Vue.
  14. This looks great Ryan! And with the new admin theme, it looks even better. 👍
  15. Changing the title in the SEO tab only affects the SEO title (<meta property="og:title" content="...SEO title...">). Your page title in the browser is the one you set in the <title> tag of your HTML. If you are referring to Google showing the old one, then you will need to wait a while for it to be re-indexed. Edit: I apologise, it seems I'm incorrect. MarkupSEO will include a <title> tag for you if you fill out "Title Format" in that case, make sure you don't have your own <title> tag as well.