Closed slaFFik closed 7 years ago
Add to your install's wp-config.php:
define('SCRIPT_DEBUG', true);
That fixed the initial issue, thanks.
I believe there is no need to report individual CSS issues on various pages? Working with 2015 theme.
@slaFFik While the focus of my work to date and currently is across a range of tasks, functions, files structures, templates, css styles etc In terms of the base level styles needed and in terms of getting various templates and functions working I am using 2017 only to work to and am specifically disregarding the notion that BP is not really a theme and all the issues that that statement brings to the table as thats too much to deal with at this stage. Or in other words I'm pretending this is a theme and that theme is 2017 :)
Reporting style issues is likely something that will come later, unless there's something really dumb happened, ideally I'm looking to try and find solutions for a broad range of style issues managed & contained within the partial import files but not sure how well that's going work out.
2017 - no problem, I will switch to it.
Individual css issues - will ignore for now, will pay attention to more global problems.
Thanks!
We need to make sure that production instances are ready to use bp-nouveau.
This means that we have to be ready to minify all our CSS and JS assets (also see #158) so that bp-nouveau will work when SCRIPT_DEBUG
is set to false
.
for all BuddyPress pages: single items, directories etc.
It looks like this: