Upload Avatar get error

DearTanker

Oops! Something went wrong on the server. Please reload the page and try again.
I have already install image_magick-6.8.8.10

d1a8lo24

Yggdrasil
McAtze
DearTanker

No it all depends on your host, server environment and many other things that I wish I knew.

I have install it on XAMPP on a windows machine running windows 10 and the latest version of XAMPP and accessing it through localhost and locahost/subfolder without any problems.

I have also install it on a virtual server on godaddy running centos 6 an CPANEL WHM on domain under the root of the main domain, sub folder and sub domain like so: domain.com, domain,com/forum, forum.domain.com

So no it doesn't need to be on a domains root folder.

Even though this is still a BETA release most problems have arise from the different types of server environments and PHP configurations.

With that said and like it is stated on the documentation and installation page this is a BETA release of Flarum not intended to be use on a live site is only for testing and if you want to use it for a live site USE IT AT YOUR OWN RISK.

Any issues at this point will not be solve immediately so you just have to wait and be patient.

Now because Flarum uses different packages/libraries like laravel and others, many of these libraries require certain PHP settings/modules/extensions to be either turn on or off.

As far as I know with the first beta in order to create the avatar when uploading an image you need to have ImageMagick install on your server and imagick for your PHP installation.

Also you need to have mcrypt which should already be on your PHP installation but if not install it or enable it through the PHP INI file.

Also make sure to have PDO and pdo_mysql installed and enable on your PHP INI file

The following extensions are also required to be installed and enable in your PHP INI file.
mbstring, openssl, json, gd, dom, fileinfo, tokenizer

Not all server environments are equal and not all share hosts will allow you to overwrite these settings or give you access to the PHP INI file.

So hopefully you're able to set your own environment and have access to install an enable these settings.

If you're still experiencing problems make sure your PHP configuration has the setting display_errors enable. To see whats going on with your server and why is it having a problem. That way you can give more information on whats going on.

Amgaa

DId u check permission of assets/avatar folder?

rdn

I have this problem also, but fixed now after I installed Imagick/php imagick.

mahfudz

rdn Agreed!

DearTanker

Is about fileinfo 🙂

McAtze

I also had this error. The avatar folder had perm 777 and imagick is installed ..
What can i do?

Yggdrasil

McAtze Do you run Flarum from a subfolder? Franz said to me in another thread that it might not work because of that. We have to wait for the next beta where this problem is already solved.

McAtze

Yes, it runs as a sub. I also can't create any posts or something ..

annso

I have the same problem, and my installation is in a subdirectory. I can see that my avatar is in the assets/avatar/ directory, but the URL generated by Flarum is not right (the subdirectory is missing in the URL). While we wait for this issue to be fixed, maybe we could make it work with some Apache/Nginx redirect rule or something ?

luceos

This is a known issue and solved for beta 2: https://github.com/flarum/core/issues/291

Dominion

As luceos said, it's been fixed. Hold on for just a bit longer...

Gizmo

Works fine for me

Yggdrasil

Just installed Flarum anew on my webspace, this time in the main folder of the domain. Sadly it still doesn't work. Seems that it really needs to be in the root folder of the whole webspace, which is often not possible, as most of them want you to use a extra subfolder for every domain.

Fastidious

d1a8lo24 it will be easier (for those having problems now, and those who will have problems later) if the exact requirements were listed, or--and this is more important, I think--the installer had a way to check for all those things you mention, and let people know more.

On one hand we want to make it easy for documentation contributors, but on the other we are limping. It is beta, though, and thus bound to get better.

Franz

Fastidious it will be easier (for those having problems now, and those who will have problems later) if the exact requirements were listed, or--and this is more important, I think--the installer had a way to check for all those things you mention, and let people know more.

Yep, this is already implemented in Beta.2 🙂 And we'll get better at detecting these, once more issues crop up.

d1a8lo24

Fastidious it will be easier (for those having problems now, and those who will have problems later) if the exact requirements were listed, or--and this is more important

That is very true, but on a beta release is very hard to get everything right specially when there are so many server and PHP configurations so you really never know what to expect with certain configurations.

So as a beta tester, this means anyone who wants to download the beta release since that is the purpose of a beta software to be tested, its recommended to have display_errors enable in your PHP INI file to get more detail errors and also have firebug install on your browser to see the response from the API calls.

Those are just the basic testing "tools/settings" to start, but you can use many other tools for php or your server to see whats going on, also log files are very helpful. this will give you get a better understanding on whats going on so it can be reported with details of the error.

I just believe that many people don't get the BETA concept, and when trying to report an error there are not many details being mention and this makes it really hard for anyone to get to the root of the problem.

Most of the time people are just trying to guess with out really knowing the other person's configurations and with most this has been the root of the problem

Also many people don't even take the time to read the documentation or search the discussions for the problems that they are having to see if it has already been mention.

Most "Bug reports" start like this, "I am getting a Blank Page can anyone help"
It will be nice to see something in the lines of:
I am getting blank page I am running the application on a local server, share host, virtual server, dedicated server. I do meet all the requirements to run the application and I do have all extensions required enable on PHP. what should I do"
Just very basic information helps more than none at all.

I do recommend that there should be a sticky to let people know on what to look for first before reporting any errors. And when reporting an error what type information is needed for the community to better help them. Also explain a little more on how to get errors from your machine like setting display_errors to on, on PHP, using firebug and other tools etc...

This will really help everyone find a fix or give better feed back to the developers on the application and how the application is working on different configurations.

Fastidious I think--the installer had a way to check for all those things you mention, and let people know more.

Yes that's what installers should do but sometimes because they are tied in with the main framework, they won't work correctly since the framework is starting first and the framework is already requiring certain things before the installer even starts. I am not saying that this is the case but it happens. I actually recommended for the installer to be separated from the framework it self as many applications do, this will give you a better control on detecting many configurations before even installing the application.

Tyler

Franz Is Beta.2 online now? :o....

Franz

Nope. It's almost done, though, except for one last issue (installer validation).

Tyler

Franz Ah okay! I thought I missed something... 😃 Thanks!