-
Notifications
You must be signed in to change notification settings - Fork 188
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
Pagebuilder in a specific controller #8
Comments
Hi, I would suggest you in the To manage pagesCreate a basic table view that shows pages that are stored in a To launch the pagebuilderroutes\web.php
config\pagebuilder.php
App\Providers\AppServiceProvider.php boot method
resources\views\pagebuilder\scripts.blade.php
App\Http\Controllers\PageBuilderController.php
To publicly serve all pagesroutes\web.phpAdd this at the bottom of your routes file
App\Http\Controllers\WebsiteController.php
|
Hello there, thank you very much for your help Error This my function build
` This is my model |
|
Ok perfetct!
now if i call the url "/pagebuilder/1/build" (1 is id of my page), i got the loader, but it keeps spinning forever another question: |
A layout is a default html structure in which all your page blocks will be loaded. The layouts are stored in the You indeed need to also have a record in the |
now miss the assets if i try to open "/assets/pagebuilder/grapesjs-touch.min.js.map" |
I know that error and have fixed it in the PHPageBuilder project. For now can you try a different browser than Chrome or do an extra page reload if the error occurs? I will soon create a new release. |
the error of asset not found disappear, thank you but got alway this |
I just made a v0.10.1 release. Could try a |
yep! now works! |
Great! You're welcome |
this is not a issue, but a request there is a way to include a plugin of grapejs? |
The way However, in this project each block has just a simple .html or a .php file and that's it. Creating blocks is now just a matter of tearing an awesome HTML5 theme apart into small snipets (i.e. blocks) and you're done. That being said, I can imagine that is still not always pleasant to do this for each new website so I am planning to create a default theme based on bootstrap that has blocks for each bootstrap component. |
that would be really cool! if I can help you let me know |
Awesome! It would be cool to have some example material somewhere, for others to quickly get started. The bootstrap theme is getting there, as well as better documentation, but at the moment I was still busy improving the system and build it while directly using it for some projects. For reference, this is what I recently quickly build: https://www.gambiabirdingtours.com using PHPageBuilder and the boilerplate (not even Laravel), based on this theme. It was really just cutting up the template, create the pages with the desired blocks, add texts, improve styling and done. I was thinking about sharing the code, but it uses a paid template so I guess I just have to do a bootstrap version in the near future. What I can share already, is an example of the theme structure I used: |
I use a cronjob to automatically take screenshots of the rendered blocks once a block has changed: https://github.com/HansSchouten/PHPageBuilder-Laravel-Screenshots. Each file contains the segment that should be added into your own project and you should run To assign a block to another group, create a
|
i'm still tring to create some block, but some block created with view.html can't be edited in page builder could you say why this? thank you |
That is correct, at the moment I did not create a sidebar settings for the input placeholder attributes, but I did create settings for a Link. So that explains this behaviour, this will be further extended. Or do you mean an actual |
i create a block like this and the text "label input" is not editable if i put text on a p tag is editable |
Ah ok, that is an obvious bug, I will make it editable in the next release. About the placeholder I was already aware that it still had to be implemented. |
Hi, I have updated the grapesjs version from 0.15.9 provided in the package to 0.17.27 by updating the import of CDN in the package due to the unavailability of many events in older grapesjs version. After updating the version I am getting error in the app.js file which is in the public/assets/pagebuilder folder, the same file which is in the dist folder of phpagebuilder package. The error is "Uncaught TypeError: Cannot read properties of null (reading 'attributes')". It occurs in other basic functionalities like changing button text or uploading image. The component is removed so accessing its attribute property is giving the error. |
good evening,
I have a project already started and running with Laravel 5.7.
I would like to give my users the possibility to create web pages through this page builder and therefore I would like to integrate this page builder into a specific controller of my project.
I tried to install it with the composer, but I can't edit the files to apply it only to a controller because they all files remain in the vendor folder and are not published in my project
The text was updated successfully, but these errors were encountered: