mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 11:19:36 +03:00
Visual Theme Error #2847
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Arkantium on GitHub (Jun 11, 2022).
Describe the Bug
I try to create a custom code in Visual Theme but i have always an error:
i have try rename the classe: ThisClassNotExistInPHPOrInBookstack
i have the same error. Bug in the Visual Theme ?
Steps to Reproduce
Read the screen :)
Expected Behaviour
Functionnal :)
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
22.04.2
PHP Version
No response
Hosting Environment
PHP 8.0.19
@ssddanbrown commented on GitHub (Jun 12, 2022):
Hi @Arkantium,
I am not able to reproduce this error in my environment.
This kind of thing could occur if the theme functions file was loaded in multiple times instead of just once.
Have you potentially altered the theme system core code or changed composer-based loading at all?
@Arkantium commented on GitHub (Jun 12, 2022):
Hi,
No modification for now :) just added the name in the .env
I have try delete cache, optimize clear and reload composer but same...
@ssddanbrown commented on GitHub (Jun 12, 2022):
@Arkantium Okay, I just noticed the error shown in the screenshot appears to be on the command line.
What exactly are you doing when this error shows?
@Arkantium commented on GitHub (Jun 12, 2022):
php artisan optimize
@ssddanbrown commented on GitHub (Jun 12, 2022):
Ah, Okay. The optimize and cache commands are not something we specifically document or support.
This occurs because the cache commands start a secondary app instance which re-includes the theme functions file, which would then attempt to re-create any classes.
To work around this you can put you classes into separate files then
require_oncethem into yourfunctions.php.@ssddanbrown commented on GitHub (Jun 16, 2022):
I'll therefore go ahead and close this off.