[TaylorJ] Blogs 1.7.2

[Taylor J]

Taylor J updated [TaylorJ] Blogs with a new update entry:

1.6.2

Bug fixes:

• Fixed the blog post title setting so it actually works, forgot to change the varchar amount in an upgrade step.
• Also updated the description for the setting to remind admins there is a minimum of 10 characters needed for blog posts by default... for now...

Read the rest of this update entry...

 

[infinitysnapz]

this update completely crashed my forum when attempting to upgrade from 1.6.1 to 1.6.2 - i also observe that the .zip is much larger here..


looking at the error logs - it seems to be an incompatibility introduced in 1.6.2 with another addon - ThemeHouse's 'Donate' addon
Fatal Error: Declaration of ThemeHouse\Donate\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure) must be compatible with TaylorJ\Blogs\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure): XF\Mvc\Entity\Structure

 

[GagGorilla]

Hello,

I found a bug! When you create a blog post, you can add images, and they display properly. However, if you try to edit the blog post and upload new images, the system shows them, but after saving, only the “Attach Image” button remains—the images are no longer visible! If you click “Attach,” you get the message: “You do not have permission!”

 

[Taylor J]

this update completely crashed my forum when attempting to upgrade from 1.6.1 to 1.6.2 - i also observe that the .zip is much larger here..
View attachment 336561

looking at the error logs - it seems to be an incompatibility introduced in 1.6.2 with another addon - ThemeHouse's 'Donate' addon
Fatal Error: Declaration of ThemeHouse\Donate\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure) must be compatible with TaylorJ\Blogs\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure): XF\Mvc\Entity\Structure

Will have a fix out for that tonight.

If you can't wait until then, I would suggest making an edit to TaylorJ\Blogs\XF\Entity\User.php on line 22 from:

    public static function getStructure(Structure $structure): Structure
    {
        $structure = parent::getStructure($structure);

        return $structure;
    }

to:

    public static function getStructure(Structure $structure)
    {
        $structure = parent::getStructure($structure);

        return $structure;
    }

 

[Taylor J]

Hello,

I found a bug! When you create a blog post, you can add images, and they display properly. However, if you try to edit the blog post and upload new images, the system shows them, but after saving, only the “Attach Image” button remains—the images are no longer visible! If you click “Attach,” you get the message: “You do not have permission!”

Will try to re-produce this tonight. Won't be included with the above's fix but should be soon.

 

[Taylor J]

i also observe that the .zip is much larger here..

This is probably due to me not setting up my testing suite properly and its probably getting bundled with the release. That'll be taken care of as well with the next x.x.X release.

 

[Taylor J]

Hello,

I found a bug! When you create a blog post, you can add images, and they display properly. However, if you try to edit the blog post and upload new images, the system shows them, but after saving, only the “Attach Image” button remains—the images are no longer visible! If you click “Attach,” you get the message: “You do not have permission!”

I was able to reproduce this as far as the images are no longer there, I have not yet to see a "You do not have permission!" message appear. Should have the fix out soon for the images not appearing when someone goes back to edit a post and adds more attachments/any attachment.

 

[Taylor J]

Taylor J updated [TaylorJ] Blogs with a new update entry:

1.7.0

This is mainly a refactor release of the codebase to bring everything more inline with best practices from the XenForo core when it comes to service files/finders/etc. Mainly only other devs would care about this.

Bug fix:

• Fixed an error when editing blog posts with and adding attachments on edit where they would not associate with the blog post or appear on re-edit/blog post view.

Read the rest of this update entry...

 

[grabacontroller]

I'm getting a php error on this new update.
Fatal error: Declaration of SV\UserMentionsImprovements\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure) must be compatible with TaylorJ\Blogs\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure): XF\Mvc\Entity\Structure in /src/addons/SV/UserMentionsImprovements/XF/Entity/User.php on line 93

 

[Goldex]

this update completely crashed my forum when attempting to upgrade from 1.6.1 to 1.6.2 - i also observe that the .zip is much larger here..
View attachment 336561

looking at the error logs - it seems to be an incompatibility introduced in 1.6.2 with another addon - ThemeHouse's 'Donate' addon
Fatal Error: Declaration of ThemeHouse\Donate\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure) must be compatible with TaylorJ\Blogs\XF\Entity\User::getStructure(XF\Mvc\Entity\Structure $structure): XF\Mvc\Entity\Structure

In the last update, the site crashed completely. I disabled it in the database, but the site still only displays an error.

 

[grabacontroller]

Ya. It crashed my site, too. Now I have to restore my account and lost data I was working on.

 

[travis_farmer]

same here...
in src/config.php, add the following lines:

$config['debug'] = true;
$config['enableListeners'] = false;

this will temporarily disable the add-ons. go to Admin CP, and disable the update for the blogs until he gets it fixed.

 

[Taylor J]

Just now seeing the above reports, looking into those now.

 

[Taylor J]

Taylor J updated [TaylorJ] Blogs with a new update entry:

1.7.1

Bug fix(es):

• Fixed error on getStructure call as it was calling : Structure while no other addons are which causes a fatal error.

Read the rest of this update entry...

 

[thieptb]

when install ==> error

 

[Taylor J]

Taylor J updated [TaylorJ] Blogs with a new update entry:

1.7.2

Bug fixes:

• Fixes a false install/upgrade requirement introduced in 1.7.1 where the add-on could incorrectly fail if the public package did not include a vendor folder.

Read the rest of this update entry...

 

[GagGorilla]

Thank you Taylor! Great Job