Closed vitali-sigel closed 5 years ago
hi, unfortunately kirby-webpack does not support kirby 3 right now The support is planned but I lack of time to make all the fixes and improvements for the migration
Okay, thanks for the fast reply!
I found a solution to this. In the release 0.9.1 you already implemented the path for the kirby router: ` let args = [ '-d', 'upload_max_filesize=100M', '-d', 'post_max_size=500M', '-d', 'short_open_tag=On',
// enable custom php router
// to handle routes with dots in it (like /default.json)
// this is needed to use content representations
path.join(user.paths.www, 'kirby', 'router.php')
] ` I just had to adjust the folder from "site" to "kirby", since the router.php lives in the "kirby" folder.
Everything seems to work perfectly now!
I'm glad that you found a workaround ! Pinning this issue for later reference.
FIY @grommas, I just created a Kirby 3 branch partially based on your fork. Feel free to PR if you want to add things.
Once properly tested, this branch will be merged in the main repository.
👋 I am using kirby-webpack with Kirby CMS 3 now and it works great, but there is a problem with the development server.
After the npm run build process and starting the build in PHP server php -S localhost:8000 kirby/router.php everything works. The images are there and even the plugin works.
So I tried to install the Kirby routing in the development server but failed.
phpServer = php({ bin: user.devServer.phpBinary || 'php', host: user.devServer.phpHost || 'localhost', root: user.paths.www, verbose: false, promptBinary: true, args, router: user.paths.kirby.core + '/router.php' // Kirby routing })
Am i missing something here? Thank you very much!