[TaylorJ] Blogs

[TaylorJ] Blogs 1.3.0

No permission to download
@TaylorJ is there any way to fix this?

View attachment 313017

View attachment 313018
Those will be changed to phrases (alongside the other ones you reported) here on the next 1.1.x release

@Taylor J it's not automatic indexable. How can we fix that?
They actually all are but I forgot to include the search template for blog's. If you create a blog post you should see it appear in search immediately, blog's will appear with 1.1.1 as well when I ship it with the proper template.
 
What versions did you both upgrade from? 1.0.0 or an earlier beta version? I still wasn't able to replicate after doing all of my previous attempts in post 256 but after upgrading from 1.0.0 to 1.1.0.
I upgraded from 1.0. I had installed a earlied beta version and had problems, remember? I unistalled and installed the 1.0. So, I recently updated to 1.1.
 
@Taylor J can you implement multi blog system please? For example, I created a blog called Horror Movie Reviews and I want to make it open to all forum members. They should be able to create their own content in this blog topic. Is it possible?
 
Me again @Taylor J 😅

Our forum members says blog title character limit is too low. They said it's 21 character and I think it's not enough. Is there any option to increase that limit?
 
I upgraded from 1.0. I had installed a earlied beta version and had problems, remember? I unistalled and installed the 1.0. So, I recently updated to 1.1.
I still haven't been able to replicate this and it is driving me up a wall. I would suggest for now to backup the tables you want (if you even want to keep your blogs) and uninstall the addon then reinstall.

I can't find anything in the setup file on the upgrade steps that would cause this on an upgrade, I'll continue to try to get this to happen to me and fix it while also pulling out my hair.

@Taylor J I can't see reacted members btw.

View attachment 313044
Hmmm.... I have no idea when this broke but will get it fixed with the next x.x.X release with the phrases. This should be out tonight/tomorrow depending on my work schedule and new workout routine at the gym later today.

@Taylor J can you implement multi blog system please? For example, I created a blog called Horror Movie Reviews and I want to make it open to all forum members. They should be able to create their own content in this blog topic. Is it possible?
The feature to add other "owners"/"allowed posters" is already planned. I didn't have or even think about making a blog possible to allow anyone/everyone to post in but will take a look into that as well. I'd have to plan out how I would want to handle members being "banned" from posting in a blog first.

Me again @Taylor J 😅

Our forum members says blog title character limit is too low. They said it's 21 character and I think it's not enough. Is there any option to increase that limit?
I can turn this into a setting I believe so forum owners can change it to their desires. Though I should note that as of right now the max length is set to 50 so I'm not sure why it's stopping them at 21...

I am facing this issues


View attachment 313078
Have you setup your user group permissions?
 
Reinstalling solved the old problem. Now I can report a new bug.

TypeError: XF\Repository\PostRepository::findPostsForThreadView(): Argument #1 ($thread) must be of type XF\Entity\Thread, null given, called in /home/e4tcom/public_html/forum/src/addons/TaylorJ/Blogs/Pub/Controller/BlogPost.php on line 37 in src/XF/Repository/PostRepository.php at line 12
  1. XF\Repository\PostRepository->findPostsForThreadView() in src/addons/TaylorJ/Blogs/Pub/Controller/BlogPost.php at line 37
  2. TaylorJ\Blogs\Pub\Controller\BlogPost->actionIndex() in src/XF/Mvc/Dispatcher.php at line 362
  3. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 264
  4. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 121
  5. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 63
  6. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2813
  7. XF\App->run() in src/XF.php at line 802
  8. XF::runApp() in index.php at line 23
This occurs when we delete the topic of comments. The blog still exist, but inacessible.
1730164510083.webp
Maybe will be cool if we can delete and then link an other topic for discussion, like XFRM.
 
Reinstalling solved the old problem. Now I can report a new bug.

TypeError: XF\Repository\PostRepository::findPostsForThreadView(): Argument #1 ($thread) must be of type XF\Entity\Thread, null given, called in /home/e4tcom/public_html/forum/src/addons/TaylorJ/Blogs/Pub/Controller/BlogPost.php on line 37 in src/XF/Repository/PostRepository.php at line 12
  1. XF\Repository\PostRepository->findPostsForThreadView() in src/addons/TaylorJ/Blogs/Pub/Controller/BlogPost.php at line 37
  2. TaylorJ\Blogs\Pub\Controller\BlogPost->actionIndex() in src/XF/Mvc/Dispatcher.php at line 362
  3. XF\Mvc\Dispatcher->dispatchClass() in src/XF/Mvc/Dispatcher.php at line 264
  4. XF\Mvc\Dispatcher->dispatchFromMatch() in src/XF/Mvc/Dispatcher.php at line 121
  5. XF\Mvc\Dispatcher->dispatchLoop() in src/XF/Mvc/Dispatcher.php at line 63
  6. XF\Mvc\Dispatcher->run() in src/XF/App.php at line 2813
  7. XF\App->run() in src/XF.php at line 802
  8. XF::runApp() in index.php at line 23
This occurs when we delete the topic of comments. The blog still exist, but inacessible.
View attachment 313107
Maybe will be cool if we can delete and then link an other topic for discussion, like XFRM.
For now that is working as intended as comment threads shouldn't be deleted. The next x.X.x release will have the option to either enable or disable comments on a global level.

Being able to change the comment thread from one to another probably will not be a feature I add in.
 
For now that is working as intended as comment threads shouldn't be deleted. The next x.X.x release will have the option to either enable or disable comments on a global level.

Being able to change the comment thread from one to another probably will not be a feature I add in.
Hmm. It would be good to think of ways to prevent errors from being generated.

In this case, it is possible to delete a topic. This makes the blog post inaccessible. It would be good if the blog were displayed normally without comments in this case.

And if a topic were permanently deleted by accident, it would be possible to link to another topic to reopen the space for discussion. That is why I made the suggestion. Solving these two cases would prevent errors from being generated and wrong decisions by an Admin could be partially reversed with a new topic.

Oh, it would be nice to have some way to delete a blog post from this screen too.
1730225153389.webp
I think it would be interesting to place the button to delete (from public view or permanently) in one of these areas that I highlighted.
Since I deleted the topic and the post became inaccessible, generating that error, I can't delete it without deleting the entire blog.
 
Hmm. It would be good to think of ways to prevent errors from being generated.

In this case, it is possible to delete a topic. This makes the blog post inaccessible. It would be good if the blog were displayed normally without comments in this case.

And if a topic were permanently deleted by accident, it would be possible to link to another topic to reopen the space for discussion. That is why I made the suggestion. Solving these two cases would prevent errors from being generated and wrong decisions by an Admin could be partially reversed with a new topic.

Oh, it would be nice to have some way to delete a blog post from this screen too.
View attachment 313138
I think it would be interesting to place the button to delete (from public view or permanently) in one of these areas that I highlighted.
Since I deleted the topic and the post became inaccessible, generating that error, I can't delete it without deleting the entire blog.
I'll have a better way to prevent those sort of errors here in the next second point update alongside the option of turning on/off comments globally for blog posts.

That is a good suggestion for the deletion buttons, I do need to get the inline moderation tools / that button added to the blog view.
 
Another detail:
I have no more blogs and posts. I deleted to delete that bugged blog post above.
But in my profile shows that I have 2 blog posts yet.

1730259825749.webp

1730259881698.webp
The files, like, the image that was used to blog are deleted too in process or are stored in some place in files of the host?
 
Hmmm thought I fixed that, concerning the blog post count on deletion...

As for blog headers those probably aren't deleted right now on blog deletion, they are stored under data/taylorj_blogs/blog_header_images, I'll get those deleted on blog deletion in the next second point release.

Also for now, to address the error with comments not being available anymore and the blog post view error'ing out you can edit the template below until I get the next second point release out.

taylorj_blogs_blog_post_view.html
line: 247
replace:
Code:
<xf:if
    is="$blogPost.blog_post_state == 'visible' && ($blogPost.discussion_thread_id != 0 OR $xf.options.taylorjBlogsBlogPostComments)">
with:
Code:
<xf:if is="$blogPost.blog_post_state == 'visible' && ($comments OR $xf.options.taylorjBlogsBlogPostComments)">
 
Hmmm thought I fixed that, concerning the blog post count on deletion...

As for blog headers those probably aren't deleted right now on blog deletion, they are stored under data/taylorj_blogs/blog_header_images, I'll get those deleted on blog deletion in the next second point release.

Also for now, to address the error with comments not being available anymore and the blog post view error'ing out you can edit the template below until I get the next second point release out.

taylorj_blogs_blog_post_view.html
line: 247
replace:
Code:
<xf:if
    is="$blogPost.blog_post_state == 'visible' && ($blogPost.discussion_thread_id != 0 OR $xf.options.taylorjBlogsBlogPostComments)">
with:
Code:
<xf:if is="$blogPost.blog_post_state == 'visible' && ($comments OR $xf.options.taylorjBlogsBlogPostComments)">

Are you planning some update about that nowadays? For example blog edit is very important. When we get the edit option @Taylor J
 
Are you planning some update about that nowadays? For example blog edit is very important. When we get the edit option @Taylor J
I'll probably have 1.2.0 out sometime today, still adding in blog header image deletion on blog deletion, and then just testing it out to make sure everything still works.

What do you mean by blog edit though? Neither my post you quoted or the one I replied to said anything about blog editing.
 
Back
Top Bottom