Best Of
Re: open typography.scss
The boilerplate theme when used from scratch has to be installed with yarn. All scss files building up the theme can be found in yourtheme/node_modules/@vanillaforums/theme-boilerplate/src/scss
But you wouldn't change the font in the subfolder there, because if any improvemens are made to the boilerplate theme, you would update those files and your customizations will be lost.
In order to extend the boilerplate theme, you should build up a meaningful structure directly in your own folder. Take a look at how the theme for this forum here has been built. After the "normal" files are all included, custom files are also included which simply override the css that has been defined before.
Do not rewrite the boilerplate theme, extend it 😉
R_J
Re: PHP 7.3 error
It’s worth noting we’ve fixed PHP 7.3 on master. Within the next week all Vanilla developers will be running PHP 7.3 on their development machines and we already have all of our automated tests passing on PHP 7.3.
We’ve really just been waiting for XDebug to have PHP 7.3 compatibility.
Vanilla 2.8
PHP 7.0 - 7.2
Vanilla 3.0 (next release)
PHP 7.1 - 7.3
Re: PHP 7.3 error
I've split this out to its own thread.
I think there may currently be issues with php 7.3, so maybe stick with 7.2 for now. See this comment by one of the devs:
https://open.vanillaforums.com/discussion/comment/256100/#Comment_256100
whu606
Vanilla 2.8.1 - Clicking on notifications gives 'invalid CRSF token' error [RESOLVED]
I've upgraded a Vanilla install to 2.8.1 and everything seems to work as expected, with the exception of notifications.
When clicking on the notifications I get the following pop-up
I've run utility/update successfully, but no change.
Users can change notification preferences, they just can't access notifications.
Anyone got an idea where I should start looking?
Thanks.
whu606
Re: multiple vanilla forums and memcached?
The memcached options in the Vanilla Forums Documentation look good. You can find more memcached options here: http://php.net/manual/en/memcached.constants.php
Looks like Vanilla processes the constants in the config keys to their values. Here are some of the values of the memcached options for your reference: http://php.net/manual/en/memcached.getresultcode.php#105089
Re: Welcome to the new OSS theme!
Well done! It's looking gorgeous and I can't wait to see the first themes designed based on the boilerplate 😃
If you are looking at the Activity from mobile, the delete symbol could have more margin to the right side:
The pager prev/next buttons don't have any space between them. Not sure if that really should be changed.
What feels awkward is the scroll behaviour of the Inbox flyout: that list is longer than my screen height and it begains to scroll down only when I reach the end of the page that I'm on. Hard to describe, sorry...
R_J
Re: how to write the validation using API format
@R_J I'll note best practice for these controllers (as documented) is to always have a `$this->permission()` call even if it's an empty string. This allows "default" permissions to be enforced (if the site is configured to have escalated default permissions).
Re: how to write the validation using API format
Please don't get me wrong: I really do not want to be impolite, but what is the question?
"Validation API format" doesn't exist.
"Where" to write code depends on what piece of software you are creating. Tell us what you have and what you want to achieve and we might be able to support
"Example for validating, controller, model" - Vanilla has a great inline documentation, so if you look at any of the included models, you should be able to find examples. If you cannot understand them, show the code and ask a specific question
In order to help you, you need to help us to better understand what exactly you are asking for. I'm always happy to provide code snippets.
R_J
Re: Vanilla 2.8.1 is now available - Security Patches & Bug Fixes
Ah yes. Vanilla & RocketLoader don't work well together. I'd recommend changing your mobile theme to what you were using before. If you have concerns about it not being optimized for mobile, I'd recommend filing an issue or making a separate thread for it.
SEO is something that we pay attention to, but we're not concerned for optimizing specifically for mobile. Rather we are intending to optimize the site overall.