Flarum 0.1.0-beta.14 Released

HavocK

datitisev Update worked fine. Keep it up !

Pollux

m4v3rick Seems like the focus is on the first still visible post if scrolled with the mouse wheel.
Could this behaviour be changed somehow?

But how? If you would indicate the last visible post you would run into the equivalent problem when scrolling to the top. So you would have to switch between the two ways depending on the scroll direction.

One might consider indicating something like 14-16 of 16 at the bottom and 1-3 of 16 at the top (or however many posts are visible), but that would add noise for only little more clarity.

clarkwinkelmann

Pollux in beta 13 it seems we did switch to showing the last number when at the bottom. We can see this on this very discussion.

A change in beta 14 must have changed the behavior and now only accounts for the top post. We re-wrote a lot of the scrubber, I'm not sure if that change was a required side-effect or if we just didn't notice.

m4v3rick

Pollux
clarkwinkelmann
Pollux
askvortsov

Thanks for the clarification. 🙂

Pollux

clarkwinkelmann in beta 13 it seems we did switch to showing the last number when at the bottom. We can see this on this very discussion.

True, and at the top number 1 is only shown if, like in this discussion, the first post is longer then the screen height.

But I agree, all in all the previous solution looked better.

askvortsov

clarkwinkelmann A change in beta 14 must have changed the behavior and now only accounts for the top post. We re-wrote a lot of the scrubber, I'm not sure if that change was a required side-effect or if we just didn't notice.

With the previous approach, when clicking on the scrubber to scroll to a different post, the number would glitch back and forth for a bit (you can see this here on Discuss). That's because if we scroll based on the index of the top displayed post, but show the index of the bottom post in the viewport, you get 2 different numbers. You'll get a problem either at the top or bottom of the page anyways, depending on which system you choose, and I don't think the new approach is significantly worse than the current approach. It's also consistent with what other forum systems use.

Pollux

askvortsov You'll get a problem either at the top or bottom of the page anyways

I have a seemingly crazy idea: Show the number of the post corresponding to the place where you are in a discussion. At the beginning of the discussion, display the number of the post that is at the top of the screen, at the end of the discussion, display the number of the post that is at the bottom of the screen, and in between, display the number of the post according to its position in the discussion. For example, around post 30 of 100 (30%) the number of the post is displayed that is 30% of the height of the screen from the top of the screen.

This way we get the expected display of the first and last post and still avoid unmotivated jumps in the display of the post number.

These are the little things that no one will notice immediately in the final product, but which make the product look rounder.

nexromant

Hello everyone After updating, I go to the site - "there Was an error updating the page" - and so on endlessly! What could be the problem?

https://ibb.co/VgrZ0ks

clarkwinkelmann

nexromant can you share the output of your php flarum info?

Do you see an extension name somewhere in the error backtrace? This error is probably caused by an extension that wasn't updated for beta 14 (the array_get function no longer exists in beta 14)

nexromant

clarkwinkelmann

No extensions were installed, pure Flarum .

askvortsov

nexromant Could you try running php flarum cache:clear, deleting any cache files in storage, and ensuring that Laravel packages are running v6.x?

nexromant

askvortsov Executed the command-php forum cache: clear-did not help, manually cleaned the cache files in the storage folder-it worked!

vikasprogrammer

nexromant how did you clean the cache files in storage folder, my storage/cache is already empty, is there another cache folder?

cmwetherell

Question about upgrading. I am going to start keeping track of which extensions I use that have been upgraded so I know when to make the move. Do I need to worry about anything in the list belofw that starts with "flarum/", or are those all upgraded with the core update?

luceos

cmwetherell all flarum extensions that we bundle with flarum are always compatible with the latest release.

Bodenhaltung

Hmm, i get:

  [Symfony\Component\Console\Exception\RuntimeException]  
  The "--with-all-dependencies" option does not exist.

Composer is:

Composer version 2.0.3

Thank you!

Bodenhaltung

Bodenhaltung No one any ideas? 🙁

luceos

Bodenhaltung what was the exact command you executed?

dayatbethoven

Why is that? I installed flarum on localhost. https://prnt.sc/v9fkkh

Unity

dayatbethoven i have the same problem

clarkwinkelmann

dayatbethoven Unity as the error message point out, this seems to be something Windows-specific. You could try temporarily disabling the antivirus, adding Composer to the antivirus whitelist, restarting the system, or just waiting a bit.

Or this could be a permission issue and your CMD user is not allowed to write in the location Composer uses for its temporary files (which is probably in the user's app data hidden folder).

fragicide

Congrats on this release! This is huge!

dayatbethoven

clarkwinkelmann This is when you want to install it on hosting, what to do? I tried from php 7.2 to 7.4 just the same. curl, dom, gd, json, mbstring, openssl, pdo_mysql, tokenizer, zip are all active. http://prnt.sc/v9q5gu

Unity

clarkwinkelmann Using wampserver the problem disappeared thanks

« Previous Page Next Page »