Trying to get richfilemanager working, but the filemanager popup window is empty apart from a spinning circle in the middle.
at first I thought it was an error in the upload path, but i set this to userfiles (i have a folder with this name in my uploads folder)
Then i looked at languages, my site uses estonian (et) but no ‘et.json’ language file exists for the upload manager, so i copied and renamed ‘en.json’
didn’t help
Do I need to put anything either in UserConfig or PluginParameters in the advanced tab for the extension?I inspected code on the window and it seems to indicate E_INVALID_PAR_TYPE error while loading:
I tried the solution here but no help: Issues · psolom/RichFilemanager · GitHub got this working?General question:
Why does phpmaker generate a ckeditor folder in the root of my site and in vendor folder?
- RichFileManager extension is for use with CKEditor only.
- The CKEditor files are from Composer package (under vendor folder), they are copied to your project folder (probably because it is not good to use .js files from the vendor folder for server side PHP packages directly).
Yes I’m using CKeditor.
in cases where the there is no matching language file, does richfilemanager revert to english automatically?
Or do I have to set that in configuration somewhere?
philmills wrote:
in cases where the there is no matching language file, does richfilemanager revert to english automatically?
You may find the answer in the file filemanager.config.json.php in the extension.
In the extension this file didn’t exist.
config/filemanager.config.default.json exists, and i had to copy that and rename it.
Shouldn’t the file generation process create a valid config file?
and where is the advanced setting “UserFilesPath” supposed to be stored? It’s not in the config file…
The URL in the filemanager window is: /vendor/hkvstore/richfilemanager/index.html?CKEditor=x_Instruction&CKEditorFuncNum=1&langCode=et
This looks like its still trying to apply ‘et’ as the language, which shouldn’t be a problem as I copied en.json to et.jsonabout the file path:
According to wiki “fileRoot” => false, is used when the default path ‘userfiles’ is defined - so it seems that’s correct tooBack to the main error/vendor/hkvstore/richfilemanager/src/js/libs-main.js is generating an error:
E_INVALID_PAR_TYPE: {“expected”:“Plain Object”,“name”:“json”,“value”:"\n\n\n … etcI can’t post the full error here as it seems to contain the parent page’s entire htmlmy dev server is PHP 7.4, production is 8.1 but it doesn’t work on either
- The file will be generated by the extension to the API folder (no need to do it yourself),
- See the notes of the extension for description of the advanced settings (including “UserFilesPath”), see Using Extensions,
- You probably have PHP error with PHP 8.1, check the whole HTML returned and see if there is any PHP error inside.
As I mentioned previously, my dev server is PHP 7.4 and I get the same error there too, so it can’t be a PHP version issue
Did you remember your Composer point to which PHP version? Make sure it points out to the right PHP version on your development server.
Try also to use the same PHP version between your development and production server.
arbei wrote:
check the whole HTML returned and see if there is any PHP error inside.
You should check, regardless of PHP version.
I ran the html through https://validator.w3.org/
I cleaned up a few small things, but some issues were found actually with the PHPMaker generated code (not modified my me):
- Attribute name not allowed on element meta at this point.
- Element meta is missing one or more of the following attributes: itemprop, property
-
- Element div not allowed as child of element span in this context
- ‘close’ button in modal dialogue is missing closing tag
apart from that there’s a bunch of false positives, and some minor advisories
Those do not affect using the file manager at all. You should focus on PHP and/or JavaScript errors, did you find the PHP error in the HTML from the HTTP response?