Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

After update to 2.5.9 #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lastsamurai26 opened this issue Apr 27, 2022 · 11 comments
Closed

After update to 2.5.9 #35

lastsamurai26 opened this issue Apr 27, 2022 · 11 comments

Comments

@lastsamurai26
Copy link
Member

SQLSTATE[HY000]: General error: 1 no such column: links.custom_css (SQL: select "links"."link", "links"."id", "links"."button_id", "links"."title", "links"."custom_css", "links"."custom_icon", "buttons"."name" from "links" inner join "buttons" on "buttons"."id" = "links"."button_id" where "user_id" = 3 order by "up_link" asc, "order" asc)

I hope I didn't do anything wrong but after the update I can't access my page anymore only the admin panel.

@JulianPrieber
Copy link
Member

This is most likely due to a missing database entry. The last update added two new database entries, which you're probably missing.

Assuming you are running with the default, SQLite database, try temporarily replacing your database with the one in the zip file found here, just to be sure.

Please make a backup of your current database before doing that.

@lastsamurai26
Copy link
Member Author

Yes, I saw it :/ new indexes have been created in the create links :-D dooof can't I update them somehow ? means I have to transfer my datasets

@JulianPrieber
Copy link
Member

Honestly, I'm not even sure myself. Lemme try real quick.

@JulianPrieber
Copy link
Member

In my testing, I was not able to add the entry with the usual migrate command php artisan migrate. After some digging online, it seems to be possible to add new columns to the database with migrations, but I'm not really sure how.

I would probably just add the entries manually. Or rebuild the links from scratch.

@lastsamurai26
Copy link
Member Author

I compared both databases with each other and copied all the data records from my own database as SQL and then copied them into the new database, including the users.

Correct I have rebuilt the database manually with the "Update database".

@lastsamurai26
Copy link
Member Author

:-( I would like to help, but I don't know how this seeder works and how the migration should work. Maybe I can find a solution then you can build it in.

@JulianPrieber
Copy link
Member

About a month ago, I experimented with implementing this solution here and this would probably work for us, but currently there is a bug present in the code which makes using the thing impossible. This bug was pointed out multiple times by users, but the dev isn't actively responding to issues at the moment, so it might be awhile until this can finally be implemented.

@lastsamurai26
Copy link
Member Author

ok, if this has already been reported but the developer does not fix it, does anyone know where the error lies so that this can be cloned and then fixed?

@JulianPrieber
Copy link
Member

I tried a bit myself, but I can't really find the cause. This appears to be a simple formatting error that should be fairly easy to solve if you know what you're doing in PHP.

@lastsamurai26
Copy link
Member Author

I'll have to take a look at it and see if I can find the problem.

@JulianPrieber
Copy link
Member

JulianPrieber commented Apr 27, 2022

This issue probably describes it best: codedge/laravel-selfupdater#309. I'm fairly certain that this issue got introduced with a decently recent push, but I'm not entirely sure about the exact time frame.

The issue is that a function calling a certain URL with cURL has a syntax error, more precisely, a simple "/" is missing between the version variable and the URL.

@LinkStackOrg LinkStackOrg locked and limited conversation to collaborators Apr 28, 2022
@JulianPrieber JulianPrieber converted this issue into discussion #38 Apr 28, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants