Dreadknux Posted January 3 Share Posted January 3 I just came across some kind of configuration error when trying to move a Blog Entry from one Blog to another. The error is below (root dir info removed): Error: Call to undefined method IPS\blog\Entry::sendModerationAlert() (0) #0 [dir]/system/Helpers/Wizard/Wizard.php(181): IPS\blog\modules\front\blogs\_entry->IPS\blog\modules\front\blogs\{closure}() #1 [dir]/uploads/template_68_94a9d7649fb9cdbfc784d3516e61a717_global.php(879): IPS\Helpers\_Wizard->__toString() #2 [dir]/system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_core_front_global->box() #3 [dir]/applications/blog/modules/front/blogs/entry.php(449): IPS\Theme\_SandboxedTemplate->__call() #4 [dir]/system/Dispatcher/Controller.php(107): IPS\blog\modules\front\blogs\_entry->move() #5 [dir]/system/Content/Controller.php(50): IPS\Dispatcher\_Controller->execute() #6 [dir]/applications/blog/modules/front/blogs/entry.php(64): IPS\Content\_Controller->execute() #7 [dir]/system/Dispatcher/Dispatcher.php(153): IPS\blog\modules\front\blogs\_entry->execute() #8 [dir]/index.php(13): IPS\_Dispatcher->run() #9 {main} Here are the steps I took to get this: Locate Blog Entry Select 'Move' Choose destination Blog ("Fan Made") On destination Category page, check 'Send Alert to User', write Subject and Message. Check 'Anonymous', hit 'Send' Message above appears It seems that the Blog Entry still moved to the intended destination regardless, but I obviously have no way of knowing if the User ever received the Alert I wrote (I had to move two Blog Entries from the same person, when I tried to send an Alert for the second Entry the Message textarea "restored" the text from the last Message I tried to send, which suggests to me that IC4 failed to deliver the first Message to the User). Link to comment Share on other sites More sharing options...
Marc Posted January 3 Share Posted January 3 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. Link to comment Share on other sites More sharing options...
Solution Marc Posted March 14 Solution Share Posted March 14 This has now been resolved in the 4.7.16 release. Please update if you are seeing this issue. If you are then still seeing the issue, please let us know. Link to comment Share on other sites More sharing options...
Recommended Posts