kongondo

True, but they need a current subscription to access those boards ?.

Thanks for the explanation. Sorry, I should have been clearer ? I didn't mean that RM field. I meant the test one I requested you to set up. Or, maybe you didn't misunderstand me... ? Hmm. I am sure you have put a lot of thought into this and it does sound like a complex setup but just wondering if it would be better for the Admin App to only provide data and have a RM field in site 2 (public site) consume the data (and render it)? Of course I can't see the whole picture so my thoughts might be off base ? .

Welcome to the forums @Spencer Adding to your list: https://github.com/adrianbj/ProcessMigrator Not sure #2 does assets though.

By the way, I am wondering why you need to use RM in a multi-instance setup. Is you intention to output RM markup from site-1 in site-2? My understanding of multi-instance setups is a way to easily pass data (not markup) between sites. If you can, please also show me the code you are using to invoke RM in the second site. Thanks.

Thanks for the info. It seems that $files is only reading what is locally available to it. i.e. if I invoke $files in site-1 (where RM is) but use site-2 like so, $site1->rm_field, $files will look for the file RM is trying to render from its own file system, i.e. /site-2/templates/ instead of /site-1/templates/. This supposition is sort of supported by this: https://processwire.com/api/ref/wire-file-tools/render/ What we want is probably an absolute path to the file in site-1, maybe using $files->include(). https://processwire.com/api/ref/wire-file-tools/include/ I don't want to bother you further with more tests ? . I'll look into this when I get a moment.

Aha. OK, we are getting somewhere. I am wondering if this has to do with the new silly bug I introduced (new RuntimeMarkupUtilities) but have never gotten round to fixing. Conversely, multi-instance may still have issues with $files variable. Here's another test for you please, if you don't mind. Could you try the following (one at a time) in the test RM instance please? Instead of echoing, call your file like so: $filename = 'something';// // file will be in /site/templates/ return wireRenderFile($filename); return ProcessWire\wireRenderFile($filename); //return $files->render($filename);// @note: this SHOULD NOT work since RM doesn't know 'files' yet return wire('files')->render($filename); Are you using the Master or Dev version of RM? I haven't looked at it in a while so I am not sure what the differences are though ? Hmm. I have no clue about this one.

I am very curious about this. I am curious why both Options and RM are not working. What do they have in common? RM, as you know does not access the database and I wonder whether that is something multi-instance requires? OK. Are you able to do a quick test for me please? Could you try a test RM instance with some simple return 'hello world'; using the paste PHP option please? Thanks.

Hi @Sébastien, Welcome to ProcessWire and the forums. Perhaps not the response you were looking for but I am a bit curious about what you mean by this? What do you mean by all files? Web accessible (public) files will be available to the world, so to speak (e.g. image files in your assets folder). Protected folders/files will not be visible. Could you please clarify and/or give examples? Please clarify this. I don't understand whether you are talking about manual or programmatic access. Similar to my previous comment, please clarify what you mean by confidentiality. From whom? Things like images, css, js, cannot be hidden and the path to those assets are visible to the world. They need to be public. What type of files are you trying to hide? This is interesting. I don't have much knowledge about crawlers and others with a better grasp might chime in. My understanding though is that crawlers treat your entities as belonging to a domain? Please clarify how this access would happen. By another domain, you mean one our you site-* domains? I use multisite option 1 myself, by the way.

Thanks for reporting back. Glad it works ? Hmm. I'm wondering whether its because of some module method that these two fields (RM and Options). Have you been able to debug? Any errors or notices? Edit: In addition, how are you implementing RM's code? i.e. via a file render or code directly in the field config?

I don't think we've ever gotten to grips with this bug. It bites some people every now and then. Excellent! Glad you got it sorted ?

That line wants to execute ProcessPageView. The error means that line 53 returned null: $process = $wire->modules->get('ProcessPageView'); /** @var ProcessPageView $process */ My guess is that files were either not transferred correctly, or fully or were corrupted. FTP can be notorious for converting files on route! (ASCII vs Binary) I'd suggests this: Upload a zip of ProcessWire Unzip the files when they are on the server Install ProcessWire Upload a zip with the file assets Unzip the assets Do the database import Alternatively Install ProcessWire on the server using this script by Soma (you might need to edit it first) Follow steps #3 - 6 above Later, you can sort out your FTP file transfer settings.

You'd be setting yourself up for all sorts of complications. You really don't want to go there. How so? Manually finding files?

I am talking about multi-instance ? not multi-site. They are two different things. // public site $somePage = $pages->get('/some/page/'); // second site // create instance $site = new ProcessWire('/path/to/www/', 'http://domain.com/'); $stuffFromSecondSite = $site->pages->find("template=very-important-stuff,sort=-created, limit=3"); // do whatever with $stuffFromSecondSite No namespace issues using above.

No worries. Moved to to the right place.

@psy, Is this thread related to a module you are developing? If so, I'll move it to the module development sub-forum. Otherwise I'll have to merge it to RockFinder 3 thread ?.

I haven't done this before (split websites) but what you describe seems doable using ProcessWire's multi-instance capability. That would require that both sites are on the same server though. https://processwire.com/blog/posts/multi-instance-pw3/

By the way, a quick workaround, if you insist on living on the edge is to do the following: Edit a Media Manager field (e.g. media_manager_image) Change its Use Tags setting and save Revert the change to what it was before and save again Uploads should now work. Note though that using the 'Cleanup' feature might still throw the PDO error linked to in the post above.

Hi all, A recent change in ProcessWire has partly broken part of Media Manager's upload feature (see the screenshot in this post with the PDO error, thanks to for @Mustafa-Online reporting). My strong feeling is that it has to do with the recent changes to the Database Class(es). I am looking into this and will report back as soon as I can. Thanks.

Please check PM. Thanks.

Please confirm where exactly in the assets folder. With the settings you've shown me, they should be in /site/assets/MediaManager/jqfu/.files_no_show. Please also confirm: Are you on MAMP? Are you on a Windows or a Mac or other? Is ProcessWire installed in a sub-folder? Sorry for the hassle. I'd really like to get to the bottom of why for most MM works flawlessly and for a few others there are upload issues. Thanks.

@Mustafa-Online, What are you Media Manager settings for the following? After Uploading Image Extensions Have a look at the dev tools, network tab, xhr when uploading: Are the files posted? What response does the server return? Do you have the following directories under /site/ ? /sites/assets/MediaManager/jqfu /sites/assets/MediaManager/uploads Btw, post_max_size needs to be bigger than upload_max_filesize. See this post by Horst. Could you try with config->debug=true and TracyDebugger and let me know if you get any errors please? I have just tested with the latest dev version and it works OK.

No idea then, in that case, sorry ?

Hi @Mustafa-Online, Thanks for the purchase. Sorry about this. Please check and confirm the following: post_max_size memory_limit file_uploads upload_max_filesize In addition, please confirm the following: What are you trying to upload? Are they perhaps smaller/larger than what you have in the settings for minimum/maximum sizes? Is this a multilingual site? ProcessWire version. PHP version. Thanks.

If the methods are still empty as in your example or populated?

@SlackMcKracken, Welcome to the forums ?