I'm trying to import my page tree from a different server, yet when i press preview all pages show the error message: "One of the inputs were not an array!"
Both servers run typo3 v11.4.0
Changing import options does not help.
Changing export options does not help either.
Creating a new,empty root-Homepage with extensions disabled does not help.
Importing with extensions disabled does not help.
Ignoring the error message and importing anyway crashes the server and requires a typo3 reinstall.
I'm happy about any suggestions where to look further into this.
Screenshot of the import screen with Error
Thanks!
After reinstalling multiple times, repeating the same steps (using option: force uid) and ignoring the error message it worked.
Related
I am currently working on an IOS app built through Swift on Xcode. Firebase packages are installed using Cocoapods, and all pods are updated. Additionally, I double-checked that the Plist and Google-Service Info files are correct.
This is the full error line I receive when logging into the app and trying to retrieve user information from the database:
nw_proxy_resolver_create_parsed_array [C3.1.1 proxy pac] Evaluation
error: NSURLErrorDomain: -1003
I am unable to figure out how to resolve this issue as there were no changes in my code and it was working beforehand perfectly.
I can provide code snippets if needed but since the app was working prior, I am assuming this isn't related to my code.
The only time I was able to solve this issue temporarily was to reset the package caches through XCode, allowing me to view posts and other content pulled from the firebase backend. Unfortunately, after I restarted the app, this solution did not work anymore, and the same error from above popped up. Since resetting the package caches worked initially, I am assuming there is no direct correlation between the error and my source code.
Does anyone have any idea as to ways I can solve this issue? It has prevented me from working on my app for several days now. Thanks for any help!
Update: After looking over my code one more time, I found that there was a missing dot in a line of code, leading to my IOS app not running. This did NOT solve the error of nw_proxy_resolver_create_parsed_array [C3.1.1 proxy pac] Evaluation error: NSURLErrorDomain: -1003, but since the app is working successfully, my problem is solved.
i set up a new TYPO3 project with the new version 11.
Since I need a form on one of my pages, I wanted to configure it within the form configuration. But if I click on "create new form" everything I get is a loading window.
Has anyone encountered the same error? I went through my error logs but couldn't find any errors there.
Thank you for your help!
This is a known bug that is fixed by the two patches linked in https://forge.typo3.org/issues/93168 . It will be included in the next release.
I'm trying to connect my apps to google sign in using AWS. But, the sign in screen can't be showed because AWS keep producing error like
this :
AWSAuthUI dependency is required to show the signIn screen. Please import the dependency before using this API
my code to show signin screen:
AWSMobileClient.default().showSignIn(navigationController: self.navigationController!,)
pods:
How to solve this problem?
I stumbled here with the same error, but I'm not using CocoaPods. I'm using Carthage. However, I also have the following line at the top of my file:
import AWSAuthUI
You could try adding that, which is what the error message suggests. Now, why I'm getting the error, I don't know. I guess I'm off to do some more searching...
i am trying to import lar file - site pages and it fails because of NoSouchGroupException:
Failed Details
An unexpected error occurred with the publication process. Please check your portal and publising configuration.
com.liferay.portal.NoSuchGroupException: No Group exists with the primary key 19107
I am importing into blank site.
Any advice would be appreciated, thanks a lot!
Allright, I have found the issue, maybe it will be helpfull for somebody:
Problem was (I do not understand why...) in Calendar content - although I have never set or use it. When I uncheck calendar (in choose content section), import was succesfull.
I've created a fresh install of Moodle 2.5. I installed successfully, I thought. I have not customized the theme, so it can NOT be theme-based.
TinyMCE's file picker is not loading...whether trying to upload a file or creating/editing a course under the Course summary files section...all I get is the "Loader" star. I did some research and found no solutions that worked. Quite a few said "custom themes," but I have no custom themes yet. Now, in checking the console, I got this:
- Uncaught SyntaxError: Unexpected Identifier /lib/editor/tinymce/tinymce/3.5.8/tiny_mce.js:2
- Uncaught ReferenceError: tinymce is not defined module.js:1
- Uncaught ReferenceError: tinyMCE is not defined yui_combo.php?moodle/1374671241/editor_tinymce/collapse/collapse-min.js:1
Digging further, I found the error on tiny_mce.js with the "uncaught syntax error" is around this area (I beautified the JavaScript for better readability and it ended up on line 3344):
pi: function(h, i) {
if (i) {
c.push("")
} else {
c.push("")
}
if (a) {
c.push("\n")
}
}
I also have no clue why the page is not seeing TinyMCE as defined.
In my browsing of multiple sites, one person mentioned being able to open the file picker in Moodle 2.5 when logged in as a regular non-Moodle user. They, too, have no answer to the problem, but I tried that and the file picker did, indeed, open.
Update
I've found it's not quite just the file picker. This whole thing is tying in to TinyMCE not loading properly...with the editing toolbar capability (whether collapsed or not.) It acts as if it's a simple text editor.
I fought with it and ended up causing more problems than solutions, so I uninstalled everything, and started from scratch. I have no plugin add-ons, no fancy themes (it's the basic one it installs with), and no customization, and it's still buggy.
The console continues to say:
- Uncaught SyntaxError: Unexpected Identifier /lib/editor/tinymce/tinymce/3.5.8/tiny_mce.js:2
- Uncaught ReferenceError: tinymce is not defined module.js:1
- Uncaught ReferenceError: tinyMCE is not defined yui_combo.php?
And it pauses the debugger on practically every page with this. It's telling me that there's a problem with how TinyMCE is called in.
I've submitted a bug report, but haven't gotten the answer yet. What I'm hoping for is someone else to have had the same problem and come up with the solution, remembering there is no theme customization, no add-ons...so they can't be at fault.
As a matter of fact I also banged to this issue after upgrading to Moodle 2.5.1+, and after digging it for hours came up with a solution that made things work smooth again, I have disabled Cache JavaScript from:
Home / ► Site administration / ► Appearance / ► AJAX and Javascript
After saving the settings the file picker started working as normal. I am not sure how bad this will affect overall moodle performance and how bad it will increase the load on server and website loading overhead, but at the moment that was the only solution that I came up with.
Hope this will help...
version 2.5.1+
The FilePicker doesn't load when editing is turned on.
If you have this issue where the FilePicker hangs while loading, click on the following:
Administration | Course Administration | Turn editing off
Then refresh the page with the FilePicker that you need to use.
I'm putting this as an answer, because I received one, and I want everyone who ends up with a similar problem to know the way to solve it.
The problem was with the admin user profile settings. The Moodle team responded, and told me what to do.
It's as simple as:
Change the admin's user profile and set not to use html editor by default.
Purge all caches both in moodle and in your browser.
Make sure that in "Site administration ► Development ► Debugging" you have "debug messages = developers" and "display debug = yes"
Thanks!