LostKobrakai

I'm not sure what exactly you're building there, but maybe you could use something like flysystem's dropbox adapter to let people upload such big files to dropbox, which is far less error prone, and import from there. Tech. php can handle those files, but some hick-up in your connection (on mobile) or anything will corrupt any upload and you need to start over again. Edit: Also this is probably not a ProcessWire specific issue, until the file is uploaded 100% it's not even touched by processwire.

Not having a prefix does currently break the detection of pagination urlSegments (see here), therefore it's not supported.

The datetime error: http://stackoverflow.com/questions/36374335/error-in-mysql-when-setting-default-value-for-date-or-datetime

Into which database do you install? The test database has been removed from the default installation of later versions of mysql.

Just to make this clear: InputfieldChosen will purposefully hide the extra textarea, because it's populating it with new pages on the fly on submission.

I'm not really a friend of the session variable, so mostly personal preference.

I'd return a hashed id – two way hashing, just to to disguise the real id – with the ajax call and put that one in a hidden field.

You're using the ProcessWire namespace in that file, therefore you need to declare files explicitly as not part of your current namespace: <?php namespace ProcessWire; // … $fb = new \Facebook\Facebook([ 'app_id' => 'the_id', 'app_secret' => 'the_secret', 'default_graph_version' => 'v2.5' ]); As you seem to use pw 3.0 you could also use composer instead of manually including the package.

It could certainly be improved, but here you go. I'll probably not going to release it officially, so if someone would like to take a shot at it, feel free. WireMailTesting.zip

I've just created a custom WireMail module, which does currently plainly logs all method calls and it's parameters to a logfile. I simply installed that one locally and WireMailSmtp on the live site.

http://stackoverflow.com/questions/930900/how-to-set-time-zone-of-mysql

It should in theory, but I had issues where the mismatch came from mysql using another timezone than php, because created is "created" by sql NOW() and not in php afaik.

Maybe a timezone issue?

@bernhard Maybe because modals can be quite shitty on mobile devices? I'm not sure if you can manage to keep the url but what about a simple session redirect to this url (no modal=1)? page/edit/?id=1115&s=1&fields=snippet_repeaterblock,snippet_tag&changes=snippet_repeaterblock

If you have a composer dependency than go ahead and use composer. I'd just not use it just as the autoloader.

I would not necessarily rely on composer being installed. But you can use the new psr-4 classloader of processwire, which is shipping with 2.8/3.0. $classLoader->addNamespace('MyNamespace', $config->paths->templates . "includes/"); And if you want your module to work in both 2.8 and 3.0 simply do not use the ProcessWire namespace, which will be dynamically injected by the module/template compiler in 3.0.

Those are just for github, so you'll see the nice text below the repo and other git related files. They do not include any further translations, so no need to upload them.

There's currently only a single type of Inputfield / Fieldtype that does support the pagination feature and that's InputfieldTable (since about a week). But the support for it is in the latest pw version, if you'd like to go for it.

Simply populating a select field seems like an easy idea, but you'll still store the selection in processwire, so what happens if that element won't be available anymore by your external api? ProcessWire's db will still have the selection saved until the page will be saved the next time. Also – as the select field options are generated from your api – you won't even notice, that there's still a previous state in the db when looking in the backend because that selected option is no longer part of the select field and therefore invisible. If you've that case covered it shouldn't be to hard to simply extend Fieldtype/InputfieldSelect and just add in your custom option retrieval.

If you're just get the path than you're getting the field value in outputformatting off mode. I'd suggest using the options posted here:

$input does also have a url/httpUrl option if you're using urlSegments and you want those to be included.

$page->fields is returning a list of field definitions, but not the data stored in those fields of the page. You want to search the section_repeat's data array like this. $page->section_repeat->find("section_title=Section 1");

I've updated the module with some small changes. Exceptions are no longer unintentionally catched when using the CLI tool. Also the default migration format does now include seconds in the timestamp. These are optional so migrations without seconds will still work.

I can certainly see your intent and I think it's ok that you want to let people know about problems in redactors pricing strategy. But this is not the place to discuss this in more detail than that. This part of the forum is just a loose wish list for ProcessWire, which happened to have a topic about redactor. We're by no means promoting or otherwise suggesting anyone to use redactor and even if this topic convinced you initially to use redactor your problem is not related to us. As I said I support you trying to simply warn other people, but everything else is just not our business.

You'd create each field separately, so you can "rollback" each field separately, too. Migrations are not bound to "a specific development step" or alike. Just add as many as you need to bring the installation to the state you need. Rollback's are also the way to go if you made some mistakes. Just rollback the migration, change your mistake and rerun it. If you've already shared the migration, or you've already saved data you want to keep, you could also add another migration, which does only correct your mistake, e.g. for your example just set the field limit and save this change.