Devflarum - Sandbox Server

Kulga

Ah yeah..

2017/06/08 13:44:20 [error] 26009#26009: *538316 FastCGI sent in stderr: "PHP message: PHP Warning:  Invalid argument supplied for foreach() in /www/devflarum/forum/storage/views/ff7171ca3d43f941c1ca0c2215094862 on line 8" while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: devflarum.xyzz.work, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7-fpm.sock:", host: "devflarum.xyzz.work"

Well, I presume that just means the the current dev-master is broken. :\

luceos

Kulga would you be able to trace that to the view and the line, I'd like to take a look or report the bug so this doesn't happen after a release.

MISC

Franz I am still experiencing this problem in an new installation ...

Kulga

luceos

2017/06/12 06:59:26 [error] 26010#26010: *639587 FastCGI sent in stderr: "PHP message: PHP Warning:  Invalid argument supplied for foreach() in /www/devflarum/forum/storage/views/ff7171ca3d43f941c1ca0c2215094862 on line 8" while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: devflarum.xyzz.work, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7-fpm.sock:", host: "devflarum.xyzz.work"

www/devflarum/forum/storage/views/ff7171ca3d43f941c1ca0c2215094862:

<?php
$url = app('Flarum\Forum\UrlGenerator');
?>
<div class="container">
    <h2><?php echo e($translator->trans('core.views.index.all_discussions_heading')); ?></h2>

    <ul>
        <?php foreach($document->data as $discussion): ?>
            <li>
                <a href="<?php echo e($url->toRoute('discussion', [
                    'id' => $discussion->id . '-' . $discussion->attributes->slug
                ])); ?>">
                    <?php echo e($discussion->attributes->title); ?>

                </a>
            </li>
        <?php endforeach; ?>
    </ul>

    <a href="<?php echo e($url->toRoute('index')); ?>?page=<?php echo e($page + 1); ?>"><?php echo e($translator->trans('core.views.index.next_page_button')); ?> &raquo;</a>
</div>

datitisev

I got this same error as well. It seems to be your PR about private discussions & posts, @luceos.
git checkout 4c0339c30e46f9a2d6bc434a4063fcd8c34b0481 works fine (the previous commit).

luceos

datitisev interesting it breaks on a foreach, I'll look into it ?

luceos

datitisev I'm not sure, I just tried creating a project with dev-master, I also updated a test install to dev-master, but I can't reproduce this ?

datitisev

luceos Huh.... maybe an extension breaks it.
These are my dependencies:

{
  "flarum/flarum-ext-akismet": "dev-master",
  "flarum/flarum-ext-approval": "dev-master",
  "flarum/flarum-ext-auth-facebook": "dev-master",
  "flarum/flarum-ext-auth-github": "dev-master",
  "flarum/flarum-ext-auth-twitter": "dev-master",
  "flarum/flarum-ext-bbcode": "dev-master",
  "flarum/flarum-ext-emoji": "dev-master",
  "flarum/flarum-ext-english": "dev-master",
  "flarum/flarum-ext-flags": "dev-master",
  "flarum/flarum-ext-likes": "dev-master",
  "flarum/flarum-ext-lock": "dev-master",
  "flarum/flarum-ext-markdown": "dev-master",
  "flarum/flarum-ext-mentions": "dev-master",
  "flarum/flarum-ext-pusher": "dev-master",
  "flarum/flarum-ext-sticky": "dev-master",
  "flarum/flarum-ext-suspend": "dev-master",
  "flarum/flarum-ext-subscriptions": "@dev",
  "flarum/flarum-ext-tags": "@dev",
  "flarum/core": "@dev",
  "datitisev/flarum-ext-dashboard": "@dev",
  "datitisev/flarum-ext-reactions": "@dev",
  "datitisev/flarum-ext-debugbar": "@dev",
  "kassius/flarum-brazilian-portuguese": "^0.1.1",
  "flagrow/masquerade": "^0.1.0@beta",
  "milescellar/flarum-ext-french": "^1.0"
},

Kulga

Devflarum reverts to only the default extensions. It may be in flarum/core as I tried disabling all extensions and it continued to occur.

luceos

Kulga or @datitisev is that column existing in your set up? It is on mine on every clean install of dev-master. Can you also re-run php flarum migrate?

datitisev

Um... Wel... @luceos You can see the full error at https://devflarum.xyzz.work/api/posts lol ?

I hope that helps you to solve the problem! Maybe the migration doesn't work well / as intended?

datitisev

luceos The column is_private does not exist when I simply checkout master.

I am not able to run php flarum migrate because php flarum gives me an error. But you are helping me see if we can resolve this issue ^_

luceos

@Kulga this was solved for @datitisev by setting the host in config.php to 127.0.0.1 instead of localhost, can you try if that works for you? Then migrate.

Kulga

php flarum migrate solved it

Migrating Flarum...
Migrated: 2017_04_07_114138_add_is_private_to_discussions
Migrated: 2017_04_07_114138_add_is_private_to_posts
Migrated: 2017_04_09_152230_change_posts_content_column_to_mediumtext
DONE.

From now on, Devflarum will run that after a successful update (+ php flarum cache:clear)
(it should of been doing this anyways - oops)

Zeokat

@Kulga exists any chance to add an extesión to use Google Analitys?

It is a common task and maybe helpfull.

Extensions available :

Kulga

Zeokat Probably not..

The issue is how much of a possibility would it be for someone to try and start tracking anyone that came to the site.. maliciously?
While most sites will do analytics, you wouldn't want yahoo (for example) to announce, here's all the data for the last 15 minutes, who wants it (including api keys!)
I don't like to go into "ifs" - but this seems like a higher level potential for abuse, for posts like:

I have hacked flarum, I know you live in Country [State] etc etc

This I suspect occurs enough on Devflarum with just generic messages, even though it's rarely seen, since trollers must not realize everything is reverted ?

Dafterz

@Zeokat Got it! Yeah, now i have Google Analytic Extension.
Thank you Flagrow and @sijad for making a lot of Usefull Extension. I Love it! ?

Pollux

Devflarum is down (since yesterday evening at least)

503 Service Unavailable

This forum is down for maintenance.

Kulga

Pollux Thanks for letting me know. It should be working fine now.

gymocom Feel free to let me know if something is wrong.

I'll just reference this:

? If you discover a issue with the server (not accessible, passwords incorrect) trigger a reset prior to reporting it as a issue here. After a reasonable time (15-30min) it isn't resolved, report it here.

Sometimes it is simply because the dev version is broken, but I don't mind poking around a bit to see if there's something else at issue.

gymocom

Even more... I already wait few days.

Pollux

So let's remind @Kulga.

« Previous Page