Configuration Assistance

@jgoodwill01

API settings should read like:

Communico API URL = https://api.communico.co
Communico Public URL = https://myAssignedAccountName.libnet.info

Please let me know if you need any further assistance with this.

Thank you. I'm seeing some data now the Communico Plus with Filters block seems to be doing well.

Getting an error with the Communico Plus Block

ArgumentCountError: Too few arguments to function Drupal\communico_plus\Controller\CommunicoPlusController::__construct(), 0 passed in

After looking at the functionality of this module though I don't know if it's going to accomplish what I had hoped. We were looking for a solution to import communico events into drupal to index search and use them as content. Feeds is still lacking Auth 2.0 support to connect to the Communico API and the RSS provided by communico is lacking a lot of event details. I believe this module just pulls data but doesn't provide any way to make it usable in Drupal. Thanks for your help and all your work on this module. Wish it could fill our needs.

Initially, when I scoped the project I designed code to turn events into nodes, but the modules sponsor at the time blocked that vector. That feature would allow events to be indexed by search api.
I am inspired to create this functionality but it will take until 06/01/23 to roll it out.

With regards to the error you found, can you please copy paste the error message (whole stack trace if you have it), and also let me know which version of Drupal you are using. I will be starting to test this module for D10 soon.

Thank you for your feedback it's very helpful. Please look for more enhancements to this module soon.

Thanks! It's very encouraging to hear you are still in development on this module. We are currently running Drupal 9.5.9 and the block was being displayed through a paragraph.

Thanks for taking the time to respond. We are constantly trying to find solutions to improve our site, getting communico data into the system would be amazing. I've got some experience with Drupal over the years but am trying to not develop anything in house that would be too difficult for future staff to maintain. If your module was able to simplify the import process and improve visibility for our communico events without over complicating the process that would be great.

ArgumentCountError: Too few arguments to function Drupal\communico_plus\Controller\CommunicoPlusController::__construct(), 0 passed in /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Plugin/Block/CommunicoPlusBlock.php on line 88 and exactly 2 expected in Drupal\communico_plus\Controller\CommunicoPlusController->__construct() (line 31 of /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Controller/CommunicoPlusController.php)
#0 /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Plugin/Block/CommunicoPlusBlock.php(88): Drupal\communico_plus\Controller\CommunicoPlusController->__construct()
#1 /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Plugin/Block/CommunicoPlusBlock.php(29): Drupal\communico_plus\Plugin\Block\CommunicoPlusBlock->buildCommunicoPlusBlock()
#2 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/block/src/BlockViewBuilder.php(171): Drupal\communico_plus\Plugin\Block\CommunicoPlusBlock->build()
#3 [internal function]: Drupal\block\BlockViewBuilder::preRender()
#4 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Security/DoTrustedCallbackTrait.php(101): call_user_func_array()
#5 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(788): Drupal\Core\Render\Renderer->doTrustedCallback()
#6 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(374): Drupal\Core\Render\Renderer->doCallback()
#7 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(204): Drupal\Core\Render\Renderer->doRender()
#8 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(160): Drupal\Core\Render\Renderer->render()
#9 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(580): Drupal\Core\Render\Renderer->Drupal\Core\Render\{closure}()
#10 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(161): Drupal\Core\Render\Renderer->executeInRenderContext()
#11 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(175): Drupal\Core\Render\Renderer->renderPlain()
#12 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipe.php(693): Drupal\Core\Render\Renderer->renderPlaceholder()
#13 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipe.php(547): Drupal\big_pipe\Render\BigPipe->renderPlaceholder()
#14 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipe.php(305): Drupal\big_pipe\Render\BigPipe->sendPlaceholders()
#15 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipeResponse.php(112): Drupal\big_pipe\Render\BigPipe->sendContent()
#16 /websites/lexpublib.org/www/html/lexpublib/vendor/symfony/http-foundation/Response.php(381): Drupal\big_pipe\Render\BigPipeResponse->sendContent()
#17 /websites/lexpublib.org/www/html/lexpublib/web/index.php(20): Symfony\Component\HttpFoundation\Response->send()
#18 {main}

I have created a new release for this module found here:
https://www.drupal.org/project/communico_plus/releases/1.0.0-beta6 →
It contains a bugfix that will assist with the error you experienced.

I'm going to create a feature request for the new functionality.
Please look for further updates coming in the near future.

The WSOD issue was resolved by the current beta7 release here:
https://www.drupal.org/project/communico_plus/releases/1.0.0-beta7 →
Performed an overall code upgrade for D10 compatability.
Testing with PHP 8.1 successful.
https://www.drupal.org/node/3277777/qa →

I will leave this issue set to "Needs Review" for a few weeks than close if no further issues are reported.

Closing this issue due to no activity for 2 weeks.
Problem was fully addressed in version1.0.0-beta9.

Automatically closed - issue fixed for 2 weeks with no activity.