Skip to content
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

[Bug]: Blade directives not being processed in views #82

Open
BoweFrankema opened this issue Feb 1, 2025 · 7 comments
Open

[Bug]: Blade directives not being processed in views #82

BoweFrankema opened this issue Feb 1, 2025 · 7 comments
Labels
bug Something isn't working

Comments

@BoweFrankema
Copy link

Bug type

Installation

Commenter Version

2.2.5

Mode

Auth

Database

mysql

Description

Blade directives such as @commentsStyles and @commentsScripts are not being processed in the rendered views. Instead, they appear as literal strings in the HTML output.

Steps To Reproduce

Add the following Blade directives in a Blade view file:

@commentsStyles
@commentsScripts

Reproduce URL

No response

@BoweFrankema BoweFrankema added the bug Something isn't working label Feb 1, 2025
@Lakshan-Madushanka
Copy link
Owner

Are there contents in public/vendor/lakm/laravel-comments/build/ directory ?

@BoweFrankema
Copy link
Author

BoweFrankema commented Feb 1, 2025

Only one SVG file:

Image

Build directory is not present.

@Lakshan-Madushanka
Copy link
Owner

Commenter hasn't been set up. Please run the setup command.

php artisan commenter:install

and I think you are not following this step

@BoweFrankema
Copy link
Author

BoweFrankema commented Feb 1, 2025

Hi Lakshan,

I've ran through the installation multiple times, but the build files are not being added. See the attached screenshot:

Image

I've also followed the installation steps and put the directives in the correct location(s)

@Lakshan-Madushanka
Copy link
Owner

Lakshan-Madushanka commented Feb 1, 2025

This is flaky. The issue is that assets aren't being compiled to the build directory. You should see the build directory and assets in the specified path. Ensure that the public path has write permissions.

If the issue persists, please try reproducing it using the demo project.

@BoweFrankema
Copy link
Author

I'm unable to replicate this issue in the demo environment, but since more reports are coming in I'll wait to see if someone else hopefully can provide more insights into what's going on here :-)

@Lakshan-Madushanka
Copy link
Owner

Log and see what's happening in the processes

private function build(string $basePath): void
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants