adrian

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"

Because you haven't specified full root paths. You need to start at /var/www/..../site/assets/....

Those are the core actions that come with the module. No - "site" actions (ones that you write yourself) are stored under /site/templates/AdminActions/ Regarding your initial suggestion - it might actually work more or less like that - I had actually forgotten about being able to call these actions via the API ? Have a read about how to do that in the docs here: https://github.com/adrianbj/ProcessAdminActions#calling-an-action-via-the-api

You can't just use that code you posted as is - you need to build it into an alternate version of the action. Copy the action file from the core actions folder to the site/templates/AdminActions/ folder, rename it and the class and modify as needed.

This thread should get you going: https://processwire.com/talk/topic/4437-delete-orphaned-filesimages-from-siteassetsfiles/ Also, once you have everything cleaned up, TracyDebugger (http://modules.processwire.com/modules/tracy-debugger/) has a Page Files panel that will help you keep track of orphaned files/images going forward.

@fruid - I guess that might work - did you try?

Jumplinks is only designed to kick in when a URL 404s. Your best bet is you place the redirect in the template file that is used to display the /recipes/ page, eg: $session->redirect('/docs/!recipes/doku.php');

Should be easy enough with a combination of https://github.com/somatonic/Multisite and http://modules.processwire.com/modules/admin-restrict-branch/

I'll admit I haven't really read your post - sorry, but I think this might do what you want based on the topic title https://processwire.com/api/ref/page/references/

@Ralf - I am glad you got the translation stuff sorted out. The "You must change your password now" text is added as a note to the "pass" field when it is rendered. So if this module is successfully redirecting to the profile editing screen of LRP, then it should display that note - if not, then it might be a question for Ryan to see if he can support this module within LRP by displaying the note, or suggesting some other way for this module to inject that note.

It's been a long time since I have looked at this module - there were a couple of issues related to automatic install of helper modules (those modules that are tied to another main module). That was the reason this never made it to the modules directory. If I find time I'll take another look, unless of course someone else is keen on seeing what they can do ?

Hi @Ralf - that checkbox field label, description, and notes should be translatable already. You can see here on a site I have with English and Portuguese: The "load on frontend" option should make it work with LRP. I did just commit one change that allows translating of the note that says: "You must change your password now". Hope that gets you going.