syntax error, unexpected 'class'

AlexL

Hello Community,

I Flarum Beta 2 and suddenly have this error:

Parse error: syntax error, unexpected 'class' (T_CLASS), expecting identifier (T_STRING) or variable (T_VARIABLE) or '{' or '$' in /www/htdocs/xxxxxxx/cms/forum/flarum/vendor/flarum/core /src/core/CoreServiceProvider.php on line 35

I have not visited my forum two weeks and now that appears.

Maybe someone can help me?

Thanks in advance.

Franz

Which PHP version are you using?

luceos

Franz your assumption is correct, I also guess this has to do with the ::class which is introduced in php 5.5.

AlexL

Now the forum is back to PHP 5.6 and at once the Forum has emerged. I do not know whether there is now a difference between PHP 5.5 and 5.6.

But now I can unfortunately not install extensions and add no tags and do not change the avatar. I could still three weeks ago. Debug is turned on and nothing is displayed.

AlexL

At least one error by the Google Chrome Inspector is me now displayed and this looks like this:

flarum.wpzweinull.ch/api/users/1/avatar Failed to load resource: the server responded with a status of 401 (Unauthorized)

It's always this /api directory, but where does it come. I do not have this directory in the FTP account.

The same error occurs in the backend of Flarum if I want to create tags or want to change something. Who has a tip? Thank you in advance.

fetch404

AlexL As far as I am aware, there isn't an actual /api directory. What you're seeing is a Laravel route, which looks exactly like a directory URL. Are you sure you configured your rewrite/htaccess correctly?

AlexL

Hello there,
OK, that's good to know that there is not the / API directory that way. My current .htaccess file looks like this, and I have Flarum on a subdomain: http://flarum.wpzweinull.ch

AddHandler cgi-php56 .php
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteBase /

. * RewriteRule - [E = HTTP_AUTHORIZATION:% {HTTP: Authorization}]

RewriteRule ^ api (. *) $ Api.php [QSA, L]
RewriteRule ^ admin (. *) $ Admin.php [QSA, L]

RewriteCond% {} -f REQUEST_FILENAME!
RewriteCond% {REQUEST_FILENAME}! -d
RewriteRule ^ (. *) $ Index.php [QSA, L]

# MultiViews can mess up our rewriting scheme
Options -MultiViews
</ IfModule>

I also suspect that it's .htaccess is, but I have not changed and only RewriteBase I have so or should I RewriteBase disable completely?

Thank you in advance.

luceos

Why are all files in your htaccess capitalized? For instance the file Api.php is by default named api.php. If you change this filename in the htaccess without changing the actual file on disk you might run into the issues you describe. If you're running on *nix file naming is case sensitive.

Also I advise against capitalizing the actual file on disk, because it will prevent forward compatibility.

On further inspection, also the RewriteRule have been changed, the spaces after ^ and before $ are incorrect. I advise you to compare your file to the .htaccess provided in the flarum installation.

AlexL

As far as I know, I had this .htaccess file in the installation package, which I downloaded. Also do not know why the rewrite rules looked like this.

I now have uploaded your hand recommended .htaccess file and still receive error messages such as these:

POST http://flarum.wpzweinull.ch/api/tags 401 (Unauthorized)

They always say that the resource can not be loaded.

Probably I still have something wrong in the installation, but just what exactly ?!

The .htaccess file should be good now.

Franz

No, that's actually an error thrown by Flarum itself, so the rewriting works now.

When exactly does this occur?
I am assuming that somehow the Authorization header is being removed by your server - which is something that this line is meant to circumvent.

AlexL

Franz OK, so the error occurs if I want to change something, for example, create the tags or install an extension in the backend or change the avatar.

Do I have to comment out your hand-mentioned line? I've tried just and that brings no success.

I had Flarum installed in the subdirectory ever and there worked the Forum almost, except that you could not add the Avatar.

Now on a subdomain I can no longer edit or create topics.