Jump to content

szabesz

Members
  • Posts

    2,922
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by szabesz

  1. No need for that as I understand it, I think. As I said, it was my impression based on my limited knowledge of the sate of this module. Seeing it in the Module Directory turns it into a different story.
  2. Yeah, I see that I'm probably banging on open doors: http://modules.processwire.com/modules/login-register/ I have not yet noticed this... Sorry for all the rumbling, I do believe this module is worth the effort
  3. As long as they are in the Module Directory. I might be wrong but others – not in the Directory – are released "as is". I might be totally mistaken but my impression is that after an initial development period, this module will not be maintained anymore and that is why it was stressed by Ryan that we are free to modify it to our needs.
  4. I'm very skeptical regarding long-term support of this module and that is the point of my post. Ryan has already shared a lot of open-source modules, and we are all grateful for that. As far as I can see, lots of such modules – which are not in the core – will not get too much attention by Ryan in the future. That is why he does not include them in the core in the first place, I guess.
  5. While I understand that fewer inputs mean fewer possible possibilities to invade the system, a non-maintained module pimped by beginners can easily be less secure than something in the core taken good care of. Just by leaving the module out of the core does not help saving ProcessWire's reputation when the modified version of this module leads to a site being hacked. I think it will be quite to the contrary should it ever happen. In my humble opinion this new module (LoginRegister) should be in the core and just like its cousin ProcessForgotPassword, they should be "uninstalled" by default. A good guide on how to implement and/or make proper changes to the module via hooks should be provided so that anyone can do it without compromising security. I vote for teaching people instead of giving them a tool with the label on it: "use at your own risk".
  6. What I meant was this: "Safari’s default insetting behavior." This means if you do not implement the new "rounded full screen" mode, then in horizontal mode the look of the design is changed by the browser because it applies a "frame" to it (they happen to call "inset"). When we have a full width header, footer, etc. design, in horizontal mode it no longer runs from left edge to right edge, and this is not optional. EDIT: the look of the design is changed in portrait mode too but in a different manner, of course.
  7. "The inset area is filled with the page’s background-color (as specified on the <body> or <html> elements) to blend in with the rest of the page. For many websites, this is enough. If your page has only text and images above a solid background color, the default insets will look great." This one doesn't sound like "optional" to me...
  8. I see, however when the process is aborted with error the only way to revert is to use something else, or am I mistaken? Also, first I tested the import process on my local environment in order to make sure it will probably work in production as well. Also, I always make batch changes to the production site around 5-6AM when actual users are very rare. Our VPS can be automatically restored in seconds provided I made a restore point in advance, of course. I'm always trying to be extra precautious
  9. Thanks @adrian! I have not yet tried your restore feature, I just made backups with ProcessDatabaseBackups and used those to restore the DB. Anyway, your action helped me a lot as I did not have to write a single line of code and all the users are imported Thank you!
  10. Just purchased Is there a private support forum for Padloper? If so, please give us access to it. Our order was from the email address with the domain ilikeskincare.com You can also write to that email address, I read those too. Thanks in advance and keep up the good work!
  11. @adrian I had some time to test the new version. My findings are: usernames with space make the import fail with error (Unknown Selector operator). Previous version worked by trimming space from the beginning and from the end, and at the same time converting spaces to dash found in-between. I did not notice the latter until now, so last time I got two users with dashes in them. At least now I know I need to fix those manually I still got timeout issue with 134 users on MAMP Pro but 32 user were ok to import. Note that current version of MAMP is rather buggy, it might be related to that or it might not. I do not really know. Otherwise duplicate user warnings were ok. For the first time (and only for the very first time) I had an issue reverting back to a database backup after the failed user import because of spaces. I used the core Revert to Backup feature and afterwards the – local staging – site was throwing a lot of: Warning: Invalid argument supplied for foreach() in .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 1257 I tried clearing the cache directory but it did not help, things got worse, the site was brought down by: User Error Exception: You do not have permission to execute this module - ProcessPageView (in .../wire/core/Modules.php line 1236) #0 .../wire/core/Modules.php(1141): ProcessWire\Modules->getModule('ProcessPageView') #1 .../index.php(53): ProcessWire\Modules->get('ProcessPageView') I replaced the database with the one from the production site and all was good afterwards. As I said, it happened only the first time, subsequent reverts in the admin did not produce this.
  12. Cool, thanks! I sent a pre-sale question yesterday, did you see it? Thank you very much in advance!
  13. Sorry to intervene with another topic but AOS stops Lister Pro from being able to list its own custom configured columns. With AOS enabled, its own "ListerTweaks" settings are enforced. It took me some time to figure out what is going on. @Rudy ran into the very same issue two weeks ago, and reported it in the Lister Pro forum as a "bug". These enforced "ListerTweaks" should be handled more gracefully I think. Fist of all, there should be an option to turn them off, letting Lister Pro do all this instead. Second, when it is turned on, there should be a notification for superusers above the listers in question as a reminder that AOS is "in effect". What do you guys think?
  14. +1 so that we do not have to deal with dependencies
  15. Hello @Jon E However, you use $page->children which is the reference to "children" in the context of the Page Tree. When dealing with page reference fields of templates, you need to reference the page reference field by its name, something like $page->my_tags for example: <?php namespace ProcessWire; foreach($page->selectedthumbs as $selectedthumb) { echo "<tr><th><a href='{$selectedthumb->url}'>{$selectedthumb->title}</a></th><th>{$selectedthumb->contributors}</th></</tr>"; } BTW: You do not need the if clause in this case, because if your PageArray is empty, the loop will not run in the first place. You left out the closing tag of <a> element If you are getting Page IDs then you are probably on the right track as that means you have a PageArray there. In ProcessWire the __toString() magic method renders the IDs when you access them as if they were strings. Meaning when you see them, you need to loop through the variable in question instead of echoing it. https://github.com/processwire/processwire/blob/57b297fd1d828961b20ef29782012f75957d6886/wire/core/PageArray.php#L579 Hope this helps. If not, please provide more code and info about the context you are having trouble with.
  16. Maybe implementing it with an ajax API call instead of a JS replacement would do the trick.
  17. I agree and I used to prefer it too but @tpr's AdminOnSteroids made me to switch to Reno.
  18. +1 Even though the new admin theme is in the works, in the meantime it could help a lot. The possibility to switch to Reno is not obvious at all for a PW newcomer, I would say Reno is kind of "hidden".
  19. By reading Ryan's blog posts I think we can deduce that these features can be considered beta for the time being. Voting for this one by adding the remark that we can clearly see he is actively working on these new features but sometimes life gets is the way too.
  20. I'll get back to this on the weekend and report my findings. Thanks a lot as always!
  21. Hi @tpr Tiny issue today which was "discovered" by me long time ago, I just did not find the time to post it... Do you happen to have Forgot Password module installed? Button centering is missing here:
  22. Thanks @adrian Yesterday I actually "only" did some preliminary tests with around 50 users. It worked well but today I had to do the "real thing". I found that it was only about 33 users I could always create without timeout, more than that sometimes worked sometimes not. Since I had to deal with only about 150 users, I created them in groups of 33 or so, as I did not want to waste time with dealing with the timeout. My other issue was that I had to deal with duplicate user names. The batcher – in such a case – fails with mysql error (...Duplicate entry 'super_duplex_user' for key 'name_parent_id'...) which is not too elegant I cleaned up the CSV to tackle this but was wondering if the script could look for them in advance? Is that out of the scope of this action?
  23. I'm glad it could help you! Yeah, in that case it is probably worth the regexp effort. When someone is not fluent in regular expression (like me ) it can be really time consuming to find the right rules if ever... But in the case of a reliable and well formatted source it is a lot easier to construct the expressions which work just right.
×
×
  • Create New...