giovannisalmeri / yellow-comment Goto Github PK

In the upcoming 0.8.1 Yellow release, content templates such as page-new-*.md are stored in a new shared content folder (/content/shared by default). The Yellow updater moves all these files from the config folder to the new location, which partially breaks the comments template. Re-uploading page-new-comments.md to the config folder solves this.
I suggest to make use of the new shared content folder.

Steffen

I get this error with the new user icon:

Hi Giovanni!
I added your plugin to my dev stage and it seems that i't was'nt installed correctly, as I can't find the files in my extension directory after putting the zip file there. So I added the files manually and also added the parameters to the yellow-system.ini. But when I access a blog post, I always see the following error (debugging enabled). How can I solve this?

Fatal error: Uncaught Error: Call to undefined method YellowToolbox::getTextArgs() in /usr/www/users/gaehna/flow/new2/system/extensions/comments.php:61 Stack trace: #0 /usr/www/users/gaehna/flow/new2/system/extensions/comments.php(142): YellowComments->onParseContentShortcut(Object(YellowPage), 'comments', '', true) #1 /usr/www/users/gaehna/flow/new2/system/extensions/core.php(855): YellowComments->onParsePageExtra(Object(YellowPage), 'comments') #2 /usr/www/users/gaehna/flow/new2/system/layouts/blog.html(18): YellowPage->getExtra('comments') #3 /usr/www/users/gaehna/flow/new2/system/extensions/core.php(685): require('/usr/www/users/...') #4 /usr/www/users/gaehna/flow/new2/system/extensions/core.php(667): YellowPage->includeLayout('blog') #5 /usr/www/users/gaehna/flow/new2/system/extensions/core.php(618): YellowPage->parsePageLayout('blog') #6 /usr/www/users/gaehna/flow/new2/system/extensions/core.php(214): YellowPage->parsePage() #7 /usr/www/users/gaehna/flow/new2/system/extensions/core.php(149): YellowCore->sendPage() # in /usr/www/users/gaehna/flow/new2/system/extensions/comments.php on line 61

Can you help to solve this problem?
Thanks in advance
René

I really do not understand this:

The plugin adds a comments section on blog pages.

To add comments on other pages create a [comments] shortcut. The following optional argument is available:

opening = overrides commentsOpening setting (see below); only the values 0 and -1 work unless the metadata of the page contain the published setting.

Can you do 1:1 clean and clear documentation how to use this plugin?

I get an email and with the email link publish a comment, which takes me to the page with the comment published. Great.

But when I go to that page on my blog again, there is no comment there, just the 'submit a comment' form.

Hi Giovanni,

I just did some searching on my site and found an unpublished comment:

Now I don't know if it's your extension or Yellow's search function.

How can I start to translate it? I don't know anything about php. How hard is it to add the feature of language files like in the other plugins?

Regards,
Chris

website returns fatal error when a comment is approved for publishing

Hi wunderfeyd,

I just updated to your last chance. Everytime I write a test comment, I just get a "An error occured. Please try again later." Is there a way to debug?

Hi - I've just installed the comments extension on my website and it is working fine - thank you!

I have a question about how to customise the text which is used in the form (for example, "Interested to discuss? Leave a comment."). I can see that you have a file in the code 'comments-language.txt' with the default text for different languages, but I can't see where that is installed on my website. I've looked in 'text.ini', and 'english-language.txt', but the text is not in there.

Can you let me know where the default text is installed?

Dom

When I turn append and auto published on. I get this error:

Warning: flock() expects parameter 1 to be resource, string given in /www/htdocs/w0080f53/nasendackel/blog/system/plugins/comments.php on line 180

Warning: flock() expects parameter 1 to be resource, string given in /www/htdocs/w0080f53/nasendackel/blog/system/plugins/comments.php on line 184

Hello,

as it seems the content-blog and content-blogpages snippet files provided with the comments plugin are not compatible with latest version of Yellow.

• The blog sidebar is not shown because the appropriate php snippet is missing.
• When clicking on a blog post in the overview, I'm being redirected to the wrong location and an error 404 is given. This only happens when Yellow is installed in a subdirectory, e.g. /yellow/blog/post points to /blog/post instead.

Hope this can be fixed and this nice idea is still under development, I'd like to test this after switching from WordPress.

Steffen

Hello,
with PHP 8.1 there is an error in th PHP script:

Warning: foreach() argument must be of type array|object, null given in /var/www/html/system/extensions/comments.php on line 314
Warning: foreach() argument must be of type array|object, null given in /var/www/html/system/extensions/comments.php on line 50

In each of the lines you can prevent this warning with
foreach ($this->comments ?? [] as $comment)

Best regards
Guenther

Can't make this work, using Yellow 0.7.x:
Alawys getting:

Comments: 0

Comments are closed.

What's missing?

If want to use it within
system/themes/templates/default.html

But I can only use:
<?php echo $yellow->page->getExtra("comments") ?>

How can I give comments an argument like [comments 0]?

If I use [comments 0] the form is displayed but only on that page, and nothing happens, commenting is not possible, does not work.

We'll keep the task list up to date.

Near future:

• lock the comment file from read to write
• timeout for unpublished/not approved comments
• blacklist
• link highlightning / image loading (whitelisted origins) inside the comments (or better Markdown)
• Emoticons (reuse emoji plugin) emoji plugin still lacks some settings/features
• icons for each individual user (created by hash of the mail address like mine on github :) ) and gravatar
• Approve mail with website authentication (for more security)
• installation and settings documentation

Beyond:

• threaded comments (reponses to specific comments already written)
• user mail validation
• user accounts / upload or select individual graphics
• comment count (how much has each user commented)

YellowComments should be renamed to yellow-comments and the yellow-extension zzz-more list has to be updated after that. Reason is the plugin naming convention for yellow.

Hi,

when you store the comments-file in the content-folder, they are published by the feed-plugin. Maybe it's a good idea to exclude.

Hi, maybe I am stupid, but how can I edit a comment via the web-interface?

Hi Giovanni,

I get the following error message when I am in CoreDebugMode: 1:

Deprecated: Creation of dynamic property YellowComment::$comments is deprecated in /www/htdocs/w01e3007/frittiert.es/system/extensions/comment.php on line 229

When I exit the DebugMode, no error message appears and the extension seems to work so far. The only bug then: I do not receive a notification e-mail.

Set last modified time for current page, otherwise the comments aren't updated by a browser refresh sometimes.

Where are the comments once they are published? How can you delete published comments, or edit them?

In line 197 and 198 there is a filter FILTER_STANITIZE_STRING. In PHP 8.1, this filter is deprecated.
You can replace this filter with FILTER_UNSAFE_RAW for a quick fix.

Comments: no should be changed to Comment: exclude and the README should be updated after that. Reason is the naming convention for extensions and settings, a key is typically singular, a value for exclusion is typically exclude. For a similar use case see command extension.

Warning: fseek() expects parameter 1 to be resource, null given in comments.php on line 167
Warning: ftell() expects parameter 1 to be resource, null given in comments.php on line 168
Warning: fseek() expects parameter 1 to be resource, null given in comments.php on line 169
Warning: fread() expects parameter 1 to be resource, null given in comments.php on line 170

No Idea what this means, but I get this error.

Hiya,
I just downloaded the zip file into my extensions folder and restarted apache (by habit).
The form does show up, but the correct labels are missing.
"[commentsComments] : 0"
was shown, instead of Kommentare: 0

By the looks of it, the file comments.txt was missing, which I plainly copied over from the zip file.

Cheers
JK

Hi, Is it possible to set comments to appear in ascending or descending order? Kind regards

Hi, Would it be possible to add a "comment count" function? In "blog-start" template I've put a link to the comment form on single post and I think it would be useful to add also the number of comments just next to that link.

I tried to use the "getCommentCount" function from your extension, but without success :)

I would appreciate your help.

@nasendackel @wunderfeyd In the readme and code templates there is a place for the developers. Now I have written "Authors", but it isn't very informative... I think I should write your (real?) names, shouldn't I? And also my name? And other contributors'? Thank you!

I tested the comment function again today and noticed that all comments are stored twice in the same location. But as already mentioned, I don't need comments at the moment, but it would be nice to be able to offer them at some point.

If you need help then, feel free to contact me.

There is the problem, that the comments file are been found by the search. Is there a way to exclude them?

For an example look at this:
http://www.nasendackel.de/search/query:sublimetext/

Hi. Thank you for the Comment addon.
I have an issue with comments showing in the main Blog page. Comment fields shows simply under blog post headlines.
I've tried to add Comment: exclude in the main Blog page, but it still shows comment field.
What do I do wrong?
Thank you.