I want to connect my Laravel 5.7.18 to parse server. But the problem is that Laravel-Parse supports Laravel 5.4 only.
I tried installing Laravel-Parse, but it produces the following error:
Installation failed, reverting ./composer.json to its original content.
It turns out the error occurs because of the Laravel version I am using (5.7.18)
How can I get this working?
Related
I upgraded Realm version from io.realm:realm-gradle-plugin:5.1.0 to 10.8.1 with no issue. However, then I had to test an earlier version of my app, so I completely uninstalled the app that used 10.8.1 from the phone and reinstalled the app that used Realm 5.1.0. I then get a crash when opening a Realm for the first time with the following error:
io.realm.exceptions.RealmFileException: Unable to open a realm at path '/data/data/com.my.app/files/fileName.realm':
Unsupported Realm file format version. (Unsupported Realm file format version) (/data/data/com.my.app/files/fileName.realm)
in /Users/cm/Realm/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp
line 101 Kind: ACCESS_ERROR.
It's like the file already exists, even after a fresh install.
I fixed this by adding Realm.delete(configuration) when the app - the one using 5.1.0 - first started just to manually delete the file the exception was complaining about. Then I removed the Realm.delete line and did another fresh install. Everything worked fine after that.
I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0
I'm trying to upgrade the Nexus installation from 3.12.x to the latest 3.15.2, which would seem like an easy task.
I have followed the upgrade guide:
Updated the nexus.rc file
Updated the nexus.vmoptions file
To match the previous version.
However the nexus run command is giving me all kinds of Exceptions which is making this very difficult:
ERROR [FelixStartLevel] *SYSTEM org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl - Failed transition: NEW -> STARTED
java.lang.IllegalStateException: Missing recipe: apt-hosted
at com.google.common.base.Preconditions.checkState(Preconditions.java:585)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.recipe(RepositoryManagerImpl.java:155)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.newRepository(RepositoryManagerImpl.java:173)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.restoreRepositories(RepositoryManagerImpl.java:264)
at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.doStart(RepositoryManagerImpl.java:246)
at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:67)
at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:56)
at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:168)
at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:100)
at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:195)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1429)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)
The system is running CentOS, but i am not sure why it's trying to use apt.
Whenever i'm pointing the data-directory to a empty dir, nexus run will successfully complete and works as expected, but obviously all the users/repositories are lost.
Does anyone have an idea?
it looks like the plugin nexus-repository-apt isn't installed on your version. make sure to install https://github.com/sonatype-nexus-community/nexus-repository-apt. The steps to install this plugin are writen into the readme of the plugin.
I think after that then nexus will work again :)
Update 2019: Sonatype included apt repository type since Nexus release: 3.17.0
no manual installation of the plugin anymore. works out of the box.
I have WordPress installed on a MAMP server. After installing some plugins I suddenly got an 'Error 500' but only when my MacBook had wifi connected.
Turning the wifi off fixes the issue, but turning it back on or uploading to a live server causes the issue to return.
After looking through the PHP log, I got:
PHP Parse error: syntax error, unexpected '<', expecting end of file
in /private/var/tmp/theme_temp_setupGlYc25 on line 2
and:
PHP Warning: Use of undefined constant REQUEST_URI - assumed
'REQUEST_URI' (this will throw an Error in a future version of PHP)
in /Applications/MAMP/htdocs/wordpress/wp-
content/themes/THEME_NAME/functions.php on line 48
Uninstalling the plugins that I had recently installed did not fix the issue, nor did re-installing MAMP or moving the installation to a new localhost.
The error is from a WordPress plugin downloaded from an untrusted source.
On installing the plugin, it wrote a number of lines of code in the functions.php file within the theme I was using which was throwing the 'Error 500' as it tried to connect to a server at 'spekt.cc'.
By following the PHP log; googling the Parse error and PHP warning, I saw a post on Medium from someone saying a similar thing happened to them with WordPress attempting to connect to 'spekt.cc'.
Using 'ack' in Homebrew, I searched my WordPress directory and found the affected files. (It had been installed on all themes within the directory)
After removing this PHP code it had inserted and removing the affected plugin, my WordPress is working fine again.
i am running a laravel project on a Puphpet VM set up (CentOS 6.4 Nginx) and all has been well but I created a new migration file and then went to run it
[code]php artisan migrate[/code]
Then got the following error message:
PHP Fatal error: Call to undefined function Symfony\Component\Console\mb_detect_encoding() in /vagrant/vendor/symfony/console/Symfony/Component/Console/Application.php on line 721
{"error":{"type":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","message":"Call to undefined function Symfony\\Component\\Console\\mb_detect_encoding()","file":"\/vagrant\/vendor\/symfony\/console\/Symfony\/Component\/Console\/Application.php","line":721}}[/code]
Now looking around etc i see people refer to the mbstring needs to be installed etc but not sure how to go about this on a VM set up, and is this an update issue as i have managed ti run migration for a while on the VM but today nothing other than the error?
i have got access to the php.ini file and uncommented the following via Vim and set them both to pass, but nothing still even after a server restart.
mbstring.http_input = pass
mbstring.http_output = pass
Any advice appreciated.
As said i am using Puphpet/Vagrant using CentOS 6.4 with Nginx, on a MAC OSX 10.7 && 10.8 running PHP5.5
You should try to install mb_string, something like:
yum install php-mbstring
Then load the .so in your php configuration
I was facing the same error today. In my case the problem was that I had a separate php.ini for CLI, where the extension was not enabled.
After adding:
extension=php_mbstring.dll
to php_cli.ini everything worked fine.