Opened 3 years ago
Closed 3 years ago
#2378 closed Defect (wontfix)
ElggFile not working on pluginsboot/system
| Reported by: | coldtrick | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Elgg 1.8.0 |
| Component: | Core | Version: | 1.7 |
| Severity: | annoying | Keywords: | |
| Cc: | brettp | Difficulty: |
Description
I'm developling a plugin where I need to handle an ElggFile on the elgg event pluginsboot / system.
however the default setting for the filestore are made on init / system. So it took me a while to figure out why I couldn't handle files.
Shouldn't the entire engine be done loading when the plugins begin loading?
so maybe a better event to start filestore_init() (filestore.php line 1468) would be boot / system
Change History (3)
comment:1 Changed 3 years ago by cash
comment:2 Changed 3 years ago by coldtrick
I needed to be sure I was before all other plugins. So I choose pluginsboot.
I agree that it's not a good to increase completity. Just thought you should know about it.
If it won't be fixed I can live with that
comment:3 Changed 3 years ago by brettp
- Resolution set to wontfix
- Status changed from new to closed
Let's keep it as it is. Closing.

I didn't write that code but I think the intention is that the pluginboot, system event is suppose to indicate that the plugin boot scripts (start.php) have been loaded.
I don't think it is a good idea to increase the complexity of the boot sequence by moving some init functions to the boot event and some to the init event. We had to do this with the views system - I think because of the upgrade and install process which may change in the future.
What is the reason for using the pluginboot event rather than the init event?