40 Replies
Emma
EmmaOP•3y ago
Emma
EmmaOP•3y ago
I'll just quickly compare this to mine. Do you get any errors when running a Blueprint command?
Element
Element•3y ago
blueprint -version
alpha-L53
blueprint -version
alpha-L53
Emma
EmmaOP•3y ago
@Element Do you get any errors when running any Blueprint command?
Element
Element•3y ago
When I run blueprint -install or -remove the only error is the permissions but that's just because the install script assumes Debian And I manually set the correct permissions afterwards
Emma
EmmaOP•3y ago
Is this only one error?
Element
Element•3y ago
Only one I noticed
Emma
EmmaOP•3y ago
Alright, that's expected.
Element
Element•3y ago
Want me to reinstall recolor and check? Yeah
Emma
EmmaOP•3y ago
Go ahead.
Element
Element•3y ago
Emma
EmmaOP•3y ago
Is it still the same problem on the admin page?
Element
Element•3y ago
The theme is there but still throws a 500
No description
Element
Element•3y ago
Affirmative
Emma
EmmaOP•3y ago
Let me just get the correct path rq.
Element
Element•3y ago
Another thing that seemed to have happened after I ran the upgrade command is everytime I load the admin page it shows
No description
Emma
EmmaOP•3y ago
Mind showing me an ls -a of the following folders? .blueprint/data/extensions .blueprint/data/extensions/recolor app/Http/Controllers/Admin/Extensions app/Http/Controllers/Admin/Extensions/recolor resources/views/admin resources/views/admin/extensions/recolor And the contents of the following files: resources/views/admin/extensions.blade.php resources/views/admin/extensions/recolor/index.blade.php routes/admin.php Expected behaviour
Element
Element•3y ago
Emma
EmmaOP•3y ago
Thank you, I'm going to read the output real quick, give me a couple minutes. It appears that something in Rocky Linux is making the Recolor route look like this:
te::patch('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'update']);me('admin.extensions.recolor.index');
te::patch('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'update']);me('admin.extensions.recolor.index');
You'll need to change that to this:
Route::get('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'index'])->name('admin.extensions.recolor.index');Route::patch('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'update']);
Route::get('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'index'])->name('admin.extensions.recolor.index');Route::patch('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'update']);
I'm not sure what is causing these weird routes. Could you try changing them and then reloading the Blueprint extensions page?
Element
Element•3y ago
Actually I think the output of cat just bugged
Route::group(['prefix' => 'extensions'], function () {
Route::get('/', [Admin\ExtensionsController::class, 'index'])->name('admin.extensions');
});
Route::group(['prefix' => 'extensions/blueprint'], function () {
Route::get('/', [Admin\Extensions\Blueprint\BlueprintExtensionController::class, 'index'])->name('admin.extensions.blueprint.index'$
Route::patch('/', [Admin\Extensions\Blueprint\BlueprintExtensionController::class, 'update']);
});Route::group(['prefix' => 'extensions/recolor'], function () {
Route::get('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'index'])->name('admin.extensions.recolor.index');
Route::patch('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'update']);
});
Route::group(['prefix' => 'extensions'], function () {
Route::get('/', [Admin\ExtensionsController::class, 'index'])->name('admin.extensions');
});
Route::group(['prefix' => 'extensions/blueprint'], function () {
Route::get('/', [Admin\Extensions\Blueprint\BlueprintExtensionController::class, 'index'])->name('admin.extensions.blueprint.index'$
Route::patch('/', [Admin\Extensions\Blueprint\BlueprintExtensionController::class, 'update']);
});Route::group(['prefix' => 'extensions/recolor'], function () {
Route::get('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'index'])->name('admin.extensions.recolor.index');
Route::patch('/', [Admin\Extensions\recolor\recolorExtensionController::class, 'update']);
});
Unless that's wrong?
Emma
EmmaOP•3y ago
That appears to be correct.
Element
Element•3y ago
That's what it is So I guess cat just messed up
Emma
EmmaOP•3y ago
Could you go into your .env and enable debug? It might be, yeah.
Element
Element•3y ago
I assume it's this you want
Element
Element•3y ago
Emma
EmmaOP•3y ago
"Route [admin.extensions.recolor.index] not defined." This seems to be the problem.
Element
Element•3y ago
Yeah
Emma
EmmaOP•3y ago
Could you try this? It should fix the issue you are facing.
Element
Element•3y ago
That did seem to fix it 🤔 I wonder what caused it
Element
Element•3y ago
No description
Emma
EmmaOP•3y ago
Blueprint uses echo to put the routes at the bottom of the file. Didn't read that "everytime" part. That isn't expected behaviour.
Element
Element•3y ago
Yeah Happens everytime I load it
Emma
EmmaOP•3y ago
iirc that also relies on echo, so it might have to do with echo being annoying
Element
Element•3y ago
Hm okay Didn't seem to do it until I ran upgrade
Emma
EmmaOP•3y ago
I don't exactly know how that could happen honestly Wait, I might know why. Are you running Pterodactyl in something other than /var/www/pterodactyl?
Element
Element•3y ago
Negative
Emma
EmmaOP•3y ago
Strange. Then I have no clue what the problem could be.
Element
Element•3y ago
Well at least the original issue is fixed Fixed it by setting the contents of .blueprint/data/internal/db/onboarding to nothing
Emma
EmmaOP•3y ago
alright

Did you find this page helpful?