adrian

@fruid - not sure about the error, but I am not using your version - add some debug code in Pageimage.php around line 1644 to see the value of the image that is trying to be installed - that should help you debug. Regarding the deleteFolder option, "false" in quotes won't work. Because this is a checkbox field, you want: 0 Look at the code in the executeAction method and you can see it casts the value as bool so 0 ends up as false, but a proper false, rather than the string "false". Hope that solves that part at least.

I don't honestly know if there are enough things hookable to make the changes you have implemented. tpr has changed a lot of functionality with the AOS module, so lots can be done, but I don't think it's necessarily easy. I expect it might be more JS than PHP to achieve what you want which seems a bit inefficient for this.

@jploch - this really does look very nice - much cleaner and more professional. I really appreciate the hard work that's gone into it and I would love to use it, but unfortunately for me it always comes back to the fact that themes in PW tend to end up out of date when Ryan applies fixes and new features so I find it's just not worth the risk. Am I the only one that feels this way?

Try: selectLocation.count=0

Perhaps you can remove them from showing up in the PWUpgrades module, because it's pretty confusing as it is and it's a new thing seeing them there.

Would you be ok with accepting a PR that allows an option to simply provide a solid font color? Also still curious about the $forceRecreation boolean not working - am I doing that wrong? Thanks.

Hi @horst - my first time using this, so sorry if this is a dumb question, but why is the text outlined rather than solid? I don't understand how to get it more legible. Is it also possible to specify the font color and perhaps also the font itself (also this is less important). Also, the "true" after the prefix doesn't seem to work - I need to keep changing the name "watermark" to something else to get it to update the image with my new settings. Am I doing that correctly? Thanks.

@bernhard - this might also be useful for getting PW's $config->ajax to work and also make Tracy capture the errors. Not sure how to do it within uikit requests. It's automatic with jquery.

@Christophe - did you see the options for this that I posted above: https://processwire.com/talk/topic/1536-module-video-embed-for-youtubevimeo-textformattervideoembed/?do=findComment&comment=206840 ?

7 months and 41 commits old ?

What version were you on? Must have been pretty old ?

Hi @MarkE - I don't think there is anything I can do at my end to fix this, but I am curious what "multi install" setup you are using. I wonder if you could confirm that you are having issues with $session / $page with AJAX calls in general and see if you can figure out a solution for that.

Those all are asking for $session via AJAX, so it looks like for some reason that is not passing through. Is it just on one PW install, or are you seeing this more widely? Can you narrow it down to something that might be server specific?

I don't think it is possible - that's the main problem - I think it should be possible to tag these modules as such. It's the main reason why my ModuleToolkit module was never officially released because there were things I just couldn't do because of this lack of properly defined relationship between modules.

That "Check for updates" option is a PW core thing - in my opinion this shouldn't show for child/helper modules that are shipped with a module, but that's a PW core issue and nothing I can change I'm afraid.

@ryan - I see that the PW Upgrades module is now seeing pro modules, which is awesome, but I wondering if you and @netcarver could work together so that his awesome ModuleReleaseNotes module can read the processwire.com git host so we don't get this error: Sorry, ModuleReleaseNotes doesn't know how to connect to the git hosting service at processwire.com. Also, PW Upgrades is reporting that FieldtypeTable has a new version: 1.0.0 but when I go to the downloads post for Profields, it still has 0.1.9 as the latest download. And, if I try to upgrade to 1.0.0, then I get this error: ProcessModuleInstall: Unable to open ZIP file, error code: 19

Oh awesome - thanks for pointing that out. I have updated the module to use this and it seems to be working fine.

Hi Ryan, Looks like a great start. First thing I noticed is that pagination doesn't work. I'll let you know if I come across anything else. I also think it's probably time to remove modules that don't support PW 3 from the sorted lists - highly liked modules that don't work with v3 will be confusing to new users.

Hi Ryan, Looks like a great start. First thing I noticed is that pagination doesn't work. I'll let you know if I come across anything else.

Looks like they finally shutdown access via http://youtube.com/get_video_info?video_id= which means I'll need to change this module to use their API which means you'll need to get an API key to make it work. Any chance you have time to make that change to the module and submit a PR?

Hi @mel47 - I am not really sure what requires you to re-save each page. Is this to fix an existing problem or is this an issue going forward as well? That saveReady hook should be fine, but you might also try Pages::added I'd need to know some more details to really help more than that.

Hi @mel47 - I don't really see how BCE relates to that "allow new pages to be created from field" setting - BCE doesn't create pages from a field - it creates them from its own interface. Can you please explain how you are using BCE - maybe I am missing something?

Glad you got it working! That's all of us really - it's more a matter of eliminating possibilities sometimes and debugging what the value of variables that are throwing errors actually are and then looking at what / how those variables are used.

I am trying to help here, but you gotta meet me half way ? If you look the code in the action, you'll see that it sanitizes the field as an integer and the options form stores the ID of the field, rather than the name. I'm sure you'll figure it out from that ?

Sorry, the issue is that $sourceFolder is empty, not the actual directory. Looks like the issue is that you are using "sourcefolder" instead of "sourceFolder"