A little color in the dashboard :)

Following the way you created the menus, I tried to create a widget system that, via Dependency Injection, allows you to add statistics, graphs, etc. on the dashboard

In the Bonfire class I added:

	/**
	 * Creates any admin-required widgets so they're
	 * available to use by any modules.
	 */
	private function setupWidgets()
	{
		$widgets =  service('widgets');

		$widgets->createWidget(Stats::class, "stats");
		$widgets->widget("stats")
			->createCollection("users");
		$widgets->widget("stats")
			->createCollection("groups");
		$widgets->widget("stats")
			->createCollection("other");
	}

The configuration takes place within each single module, which can decide to expose a widget in the isAdmin () function

For example, in the user module I added:

		// Settings widgets stats on dashboard
		$widgets = service('widgets');
		$users = new UserModel();
		$statsItem = new StatsItem([
			'bgColor' => 'bg-blue',
			'title' => 'Users',
			'value' => $users->countAll(),
			'url' => ADMIN_AREA . '/users',
			'faIcon' => 'fa fa-user',
		]);
		$widgets->widget("stats")->collection('users')->addItem($statsItem);

It is an initial version, but working.

Graphics are adaptive on a per-device basis.

What do you think?

After a fresh installation of Ci bonfire2 and startup of the php spar server -> localhost:8080, the system reports an error

mysqli_sql_exception #1054

Unknown column 'auth_identities.secret' in 'where clause' databese table is 'bf'_ prefixed as you see from other code

Currently, use paired tags (<x-foo></x-foo>) only works when we override an ini setting. This works fine when you run your own server, but anything on shared hosting will crap out. It does this to store the info in the middle $slot of the tags, and hits PHP's built-in limits, so I've currently got those turned off.

This needs to be refactored to get around this.

One idea I've had (and is just something rumbling around inside my head) would be to modify the preg_replace_callback() being currently used to modify the tag name with a unique id. It would then save the info needed to replace those tags with. This helps ensure that the correct opening/closing tags are discovered, and then the open and close tags would have to be modified separately.

Not sure if this would work as I think, and I have a feeling it would maybe lose out on some features, but I wanted to include it here so I didn't forget it when I could come back to it. Or if anyone else beats me to it.

Hey @lonnieezell, I've made a not so interesting change in order to create the PR for discussion.

After the comment I've made (https://github.com/lonnieezell/Bonfire2/issues/5#issuecomment-908423807), I now realize that the structure of Bonfire2 is quite different from what I have, so I'd like to know what you are thinking about when locating view components.

If I understand correctly, in Bonfire2, each view in a theme can access the local components in the theme folder. And it would be nice to have a way to access common base components like buttons, links, form elements, or whatever to use across themes? So, one way would be to consider the default views folder a good place to put them, or even a Components folder directly in the default app path or themes path? Or another way would be to add a Components config file where we would add other discovery paths?

Also, I'm thinking maybe we would want to share common components to multiple themes but not all. For instance, Admin and Auth themes would have the same base components that the App would not need/share. So maybe the configuration should be done in the Theme class?

One more thing, when locating components, the Theme class is called to get the path, creating a coupling that may not be ideal for the future view components library.

I don't use themes for my project yet, I have a ViewComponents config file where I put the paths to look in. Then, I compare them with the current view path when locating the Components.

Anyways, sorry for the long comment, still trying to figure things out 😅

There is a bug with this View component such that if there is a file in the writable directory, it shows up as a number instead of the file's name (and is always unwritable.) This is due to how directory_map() returns results. I have a simple fix to address this and can issue a PR, but I was wondering if we couldn't improve the Filesystem section of the System Info admin area a bit to make it more useful. For instance, since file and directories can exist in the writable area, identifying whether something is a file or directory would be helpful. Perhaps create/last modified timestamps?

Great work Lonnie PHP: 8.1.4 File: ConsentFilter.php

$cookie      = get_cookie('bf_consent');
$permissions = json_decode($cookie, true);    // Fails here because $cookie is NULL.  $cookie cannot be null, deprecated.

// Do we already have consent from the visitor?
// then nothing to do here...
if ($permissions['consent'] ?? false) {
     return;
}

Presume just need to check for null and if so go straight to consent form

Maybe I was one of the first to play around with installing bonfire 2 on web hosting.

On my testing environment localhost via apache xampp environment httpd-vhosts everything works for me because I have access to apache config files. However, we know that we do not have access to apache config (eg httpd-vhosts etc) files on the hosting, except local .htacces.

So I read the instructions on how to set up the case via .htacess I set it to the root folder /domains/brikelli.eu/public_html/ci4 where the bonfire 2 application is installed - ci4.brikelli.eu

.Htaccess content

RewriteEngine on RewriteCond% {HTTP_HOST} ^ ci4.brikelli.eu $ [NC, OR] RewriteCond% {HTTP_HOST} ^ ci4.brikelli.eu $ RewriteCond% {REQUEST_URI}! / App / public / RewriteRule (. *) / App / public / $ 1 [L]

The BONFIRE settings on the host are

.env setting is app.baseURL = 'http://ci4.brikelli.eu/' App setting is public $ baseURL = 'http://ci4.brikelli.eu/';

If you click on URl http://ci4.brikelli.eu/

The call works by calling the dasboard However, when I click login, the call loses the status 404 not found

I ask for an expert opinion. I can also help with instructions if you guide me. We definitely need to make instructions for other users not to waste time with installations but to develop applications with this system. I am sure that this way more users will join.

i read a lot on the forums i think they need to make uniform instructions

Matteo, Ljubljana Slovenia

I have created a new module to test the Recycler.

I noticed that a drop-down menu appears, but the javascript part is missing ...

I thought about implementing it, adding a javascript file inside the Recycler module;

I thought it was the best place to place it ...

I hope it will be useful.

I encountered an error following the steps outlined in the guide due to missing some requirements. I tried to fix it, but without success.

These are the steps I performed:

1. composer create-project codeigniter4/appstarter my-app --dev
2. add "minimum-stability": "dev" in to composer.json:
3. composer update
4. composer require lonnieezell/bonfire --dev

lonnieezell/bonfire dev-develop requires codeigniter4/codeigniter4 dev-develop -> could not be found in any version, there may be a typo in the package name.

I have made my own settings in the email bonfire,

however, the e-mail sending procedure wants to be sent via other parameters, The program does not return an error to the user, but it is in the system log

LOGS

Logs

Severity | Message -- | -- error | Email: sendWithMail throwed mail(): Failed to connect to mailserver at "localhost" port 465, verify your "SMTP" and "smtp_port" setting in php.ini or use ini_set()

webpackmix.js points to the missing scss directory in themes / Admin. There is already a css file already generated. package.json is missing to generate from IDE (npx mix watch)

Thank you

https://github.com/lonnieezell/Bonfire2/blob/6420c8acb0f1a3b99a730ed39c17f072497f30e0/webpack.mix.js#L4

Bumps phpstan/phpstan from 1.9.2 to 1.9.7.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Fix the following error:

Generating code coverage report in Clover XML format ... Call to undefined method SebastianBergmann\CodeCoverage\CodeCoverage::extend()
Error: Process completed with exit code 2.

https://github.com/lonnieezell/Bonfire2/actions/runs/3798657461/jobs/6460512391

Bumps codeigniter4/framework from 4.2.10 to 4.2.11.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps codeigniter/coding-standard from 1.7.0 to 1.7.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps fakerphp/faker from 1.20.0 to 1.21.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.