Leaderboard
Popular Content
Showing content with the highest reputation on 10/31/2016 in all areas
-
Thank you Sir I Have been using PW for a long time now and it´s the love of my Dev life. Just got a little worried there for a minute. My Autism Aspergers sometimes makes certain things hard to grasp, but PW has done something no other CMS could do and that is, understand it and make me want to get more advanced and indepth with its underlying mechanics. Ryan created something wonderfull here and i hope it will live on forever.9 points
-
@Michael Murphy Have already tried this one? http://modules.processwire.com/modules/process-wire-upgrade/ It does what you described but automatically. If you also have this one installed...: http://modules.processwire.com/modules/process-database-backups/ ...then the upgrade module can optionally create a db backup for you, which is recommended anyway. I recently had an issue though, but it was not the module's fault, it was a GitHub issue when github.com failed to deliver the archive of ProcessWire so the update failed too but the site was intact so no harm was done. After GitHub had come back I could upgrade without issues.4 points
-
I completely agree with @szabesz here - the PW Upgrades modules is great! I used to be all about updates via git, but this module makes it so easy. And, if you have Tracy installed you can instantly switch between any of the versions of PW that you ever installed via the upgrades module: http://processwire.com/blog/posts/introducing-tracy-debugger/#processwire-version-panel - great if you are not sure if a problem is due to a specific PW version or not.3 points
-
Hi microcipcip, good to read you again after such a long time. I remember you from a long modx time ago. How are you doing these days ? Welcome and glad to read from you again here.3 points
-
The issue is with repeater's ajax dynamic loading. It works fine when ajax option is turned off. If you can find the hook that gets called after the add new repeater child is clicked, you can probably get it to initialize the magnific call after that click. I will leave it for now since there is a workaround. I know you've got many things on your checklist ;-) Thx Rudy3 points
-
@EyeDentify, also without any asperger, it is sometimes hard to grasp things. (the forums are full of examples, ) But yep, with PW it is really nice to work. You can start with simple things and then go deeper and deeper. Every step gives you a bit more learning and understanding. And that's why you want to go deeper again. (but caution: it can be a bit addictive!)3 points
-
Your description is a bit hard to understand without a visual overview, but my suspicion (correct me if I'm wrong) is that you're building one complete form on the parent page from all child (question) pages. This would mean that the if($input->post->submit) part is executed in each included template every time you submit the form.3 points
-
I think the answer to it is yes: https://en.wikipedia.org/wiki/ASCII#Character_order Historically, numbers are listed first in dictionaries (real books) as well, at least in Hungarian books3 points
-
no worry, updating this way is fine. only changing the wire folder is enough.3 points
-
3 points
-
https://github.com/CanRau/MarkupCookieConsent/ is already doing this and Ryan fixed some missing parts some month ago..2 points
-
hi @szabesz thanks, the database backup modules is one of my default modules (probably should be in the core), but I've never tried the upgrade module - maybe I have a strong resistance to any kind of automatic update systems which goes back to some nightmare OS "automatic" upgrades on Windows and Mac Usually I have some sort of git workflow for updates, but on sites that I don't have access to the server (like shared hosting) this upgrade module might be a better and safer option than my manual upgrade process. And the module is built by Ryan then I am sure it is pretty solid and well tested. Thanks for the suggestion! thanks @adrian I have been recently using the tracy debugger and finding it very useful. That is a pretty cool integration for switching between versions, will give it a try!2 points
-
Nice. I'll check it out tomorrow! Edit: I can confirm that the fix is working. I've been able to set up multi instance with multiple language without problems. I'm a web editor at a university college's web page. And we'll be using this to integrate parts of a study guide (academic presentation of study programs and its subjects) into our main web page where our primary focus is marketing of these programs.2 points
-
I also worry about doing upgrades despite having done it so many times. The least stressful approach I have found is to rename the existing wire folder, index.php and .htaccess files, and then upload the new ones. So first I rename the existing files like this: wire-old index-old.php .htaccess-old Then I copy over the latest wire, index.php and .htaccess files. If something goes wrong during the upgrade, you can then easily delete these new files and rename the -old files. This approach feels quicker and also avoids those dialogs asking about overwriting files.2 points
-
To update those on this thread, Ryan just pushed some fixes to the dev branch which fixed this issue for me, maybe also for you. Amazing turnaround - less than 5 days (3 actual working days) from a bug submission to a working fix. Big up respect to @ryan Would be interesting to hear what people are planning to use the multi-instance support for. My initial needs are for some content migration between two sites, but I can imagine using it for much more in the future.2 points
-
2 points
-
Just a note...a PW 3 compatible Blog is on the (long? ) way (thanks to contributions form @BitPoet, etc...).2 points
-
2 points
-
2 points
-
@Rudy. Hmm, not sure that's it though. I have been having a pesky JS 'uncaught' error in MM that I haven't been able to catch myself! I don't know what it's about. What version of ProcessWire is that? No changed files? @Nukro. I'll have a think about that request. @Michael van Laar. Thanks for your interest in MM. You got some cool ideas there . However, MM itself is not a media editor and there are no plans to make it one. Unfortunately, I have never used Croppable Image 3 nor ImageFocusArea. I really have no idea how they work and/if how they could be integrated into MM. I'll try to put aside some time to look into this further, but I can't promise when, unfortunately. If such an extension ever came to light, at this point in time, it looks like it would have to be its own module, packaged and sold or distributed separately from MM.2 points
-
Just to clarify, these are backups are created by the ProcessWire Upgrades module that Ryan created. If you want to make cleaning up of these (and PW core backups) a little easier, check out Module Toolkit's Cleanup option.2 points
-
AdminOnSteroids Various admin tweaks to enhance ProcessWire admin. http://modules.processwire.com/modules/admin-on-steroids/ https://github.com/rolandtoth/AdminOnSteroids1 point
-
I have been using this module for a long time and it's been incredibly useful so I thought it was time to share. It's great for fields where you want to instruct content creators to reference something about a the page, its template, or its parent, or grand parent, etc Specify fields/properties of the page in your field's Description or Notes content, eg: [page.parent.url] [page.title] [page.template.label] You can also define a str_replace to be performed on the returned value, eg: [page.name.(-|_)] which will return the page name with the dashes replaced with underscores. An option to allow raw HTML is available. You can also use hanna codes within your description and notes fields - big thanks to @Robin S for this idea. http://modules.processwire.com/modules/dynamic-description-notes/ https://github.com/adrianbj/DynamicDescriptionNotes/ Hope you find it useful.1 point
-
This module allows you to automatically send an email to a newly created user with their username and password. It also has the option to automatically generate a password for the user upon creation. http://modules.processwire.com/modules/email-new-user/ https://github.com/adrianbj/EmailNewUser The following things are configurable: Whether Send Email option should be automatically checked when creating new user - also affects new users created via API From email address (if left blank it will use the admin email set in the config/php file Email subject Email body - includes the ability to use any fields from the user template using {field_name} codes so these can be put into the body wherever you want. It's your choice if you want to include the password in the email or not. Whether to automatically generate a password. This can be toggled on/off, but even if it is on, you can override it by simply entering a password manually when creating the new user. Ability to control the length and character sets used to make up the automatically generated password. Option to send a test email to yourself to make sure it is configured the way you expect. Because it is generally not a good idea to email passwords, it is highly recommended to use the new Password Force Change module in conjunction with this module. That way the user has to change their password the first time they login which will somewhat reduce the vulnerability of emailing the password. It can also be used for API generated users: $modules->get("EmailNewUser"); // call the module since it is not autoload on the front end $newuser = new User(); $newuser->name = 'newuser'; $newuser->email = 'newuser@gmail.com'; $newuser->sendEmail = true; // only needed if Automatic Email Send is unchecked $newuser->save(); Please let me know if you have any ideas for improvements. PS Thanks to everyone in this post: https://processwire.com/talk/topic/2981-new-user-welcome-message/ for their thoughts and ideas on how to do this.1 point
-
Done! Please let me know if you have any problems and also be sure to "Like" @Can's post over here: https://processwire.com/talk/topic/5825-multi-language-support-for-module-config-fields/?do=findComment&comment=131595 because he showed me how to add ML module config settings.1 point
-
Fixed by Ryan https://github.com/processwire/processwire-issues/issues/591 point
-
okay so you're that kind of guy..good to know.. haha..1 point
-
1 point
-
Thanks @Can - just looked through your module and have it working for my module already. Thanks so much for pointing me to this!1 point
-
Still very fresh, but I thought... what the hell... spread the PW love and give you guys a first look... https://music-room.com This was a huge project. Still lots of debugging to do, but early feedback most welcome! Don't look at the code (particularly the js)... it's a bit of a garbled mess! Ha ha! Need to, ahem, refine it over the coming weeks and months. Haven't made the jump to PW3 yet as I'm using a few modules which don't work out of the box. Thanks again to Ryan for everything. Also, big thanks to Antti for his wonderful PadLoper module. Cheers and happy browsing! Douglas.1 point
-
What i want to achieve is to be able to add an remove pages from the repeater fields. When saving the page holding the repeater field on creation everything work as expected, but later on when updating any field in the repeater the changes are not save and an error occurs. My version of ProcessWire version 3.0.36.1 point
-
Thanks for the welcoming, nice to see so many MODx devs here :). I wish I had embraced ProcessWire sooner, as after leaving MODx 4 years ago I have forked MODx Evo with other devs, then tried several other CMSs...but only in ProcessWire I find the closest resemblance of MODx Evo functionality (I hate Revo ), obviously ProcessWire is way way way more powerful.1 point
-
+1 Almost nothing is automated in our case, no need for that in ProcessWire world anyway. The only optional automation is the upgrade check, but it only happens when you log in and only if you enable it (off by default).1 point
-
Thanks SiNNut. Yeah I am aware of some new smartphone issues. I was in a mad dash to get it finished over the weekend and didn't take the time to wiggle it around. Thanks for the reminder interesting about the home page overflow issue, must have missed a tag somewhere:)1 point
-
Could you be a little bit more expressive about what exactly it is that you need? Have you just asked a question and also came up with the answer?1 point
-
@szabesz and @Macrura I setup a clean installation of pw 2.8.35, same setup as before, same database and no-problem now when "Module refresh". The only thing that I can think of is that, with this specific site I'm developing, I swapped from Osx to Windows a couple of times during development (transferring the whole pw tree structure and its database), since I have different machines (at work and at home). I think about some sort of inconsistency with WAMP and MAMP platforms, don't really know.1 point
-
This should no longer be an issue with PW 2.8 or 3.x. Is there any reason you can't upgrade to 2.8 at least?1 point
-
v095 adds a new tweak "Do not distribute modules into tabs" to ModuleTweaks. This results in a flattened module list, without duplications, which makes easier to find a module, especially when using the filter box. The "Add new module" block is in the bottom of the page. I'll probably add a jumplink to that location later for easier access. This feature is JavaScript powered and slows down the Modules page loading a bit but imo one or two extra seconds is worth for the benefits.1 point
-
If you only want to sort in-memory, getting the pages as a plain array and using a custom sort function should do the trick: <?php $ps = $pages->find('yourselector')->getArray(); usort($ps, function($a, $b) { $na = $a->name; $nb = $b->name; if(!ctype_digit($na) && !ctype_digit($nb)) return strcmp($na, $nb); if(ctype_digit($na) && ctype_digit($nb)) return strcmp($na, $nb); return (ctype_digit($na)) ? 1 : -1; }); foreach($ps as $p) echo $p->name . PHP_EOL;1 point
-
@oma I assume you want them ordered ascending and the ones starting with a number at the end. You could do this by storing the numerical names in a variable and echoing that variable after the "normal" names. $numericalNames = ""; $normalNames = ""; $names = $pages->find("template=template_name"); foreach($names as $n) { /* get the first letter of the current name */ $firstLetter = substr($n->name, 0, 1); $regexPattern = "/[0-9]/"; // if first letter is a number if(preg_match($regexPattern, $firstLetter)) { $numericalNames .= $n->name; } else { $normalNames .= $n->name; } } echo $normalNames; echo $numericalNames;1 point
-
On GitHub: https://github.com/rolandtoth/PageimageRemoveVariations On Modules directory: http://modules.processwire.com/modules/pageimage-remove-variations/1 point
-
made a note in issue tracker https://github.com/processwire/processwire-issues/issues/591 point
-
the solution provided here did not work for me! i'm using pw 3.0.36 and this worked and is even easier $fg = new Fieldgroup(); $fg->name = 'rocksvns'; $fg->add($this->fields->get('title')); $fg->add($this->fields->get('rocksvn_version')); $fg->save(); // set version field visible for this template $fg->setFieldContextArray($this->fields->get('rocksvn_version')->id, array( 'collapsed' => 0, )); $fg->saveContext(); $t = new Template(); $t->name = 'rocksvns'; $t->fieldgroup = $fg; $t->save(); tracy helped a lot here again1 point
-
@mel47 Hi, Just to let know know in case you are not aware of it that Adrian is away for another week or so, but I'm sure he will reply asap as soon as he is back.1 point
-
A small website for the Black Forest based filmmaker Markus Ketterer. You can discover his portfolio or get more informations about him by clicking the logo. Each film page can contain two film stills and two behind the scenes pictures. The transitions between the pages were made with Barba.js (thanks to @LostKobrakai for mentioning it). www.luchs.digital Modules used: ProCache ColorPicker Markup Sitemap XML Tracy Debugger Regards, Andreas Update: This website doesn't use ProcessWire anymore.1 point
-
Hi guys, This is the site: http://codekitt.com/for-candidates/ This is the job ad: https://dsr.recruitee.com/o/backend-full-stack-developer I posted it before as a short-term freelance job, but thinking about long-term now, maybe this could turn into a fulltime gig for someone.1 point
-
Thanks a lot, @adrian and @horst. You guys are awesome. As is this community.1 point
-
Hi Adrian, Many thanks for that. I've just had word from the client that the new version of your module has their application up and running again. Outstanding response time!1 point
-
I love what you've done. I could imagine you can add an extra data cleaner for the importer with the help of json_encode. Forget this, to much much my own module in my mind.1 point
-
$user = $users->get('antti'); $users->setCurrentUser($user); If you want to make the user persistent for the session (without having to do the above on every request), then do this: $session->_user_id = $user->id;1 point