Anthony Ledesma
Forum Replies Created
-
Hi @haoma, Thank you for reaching out to let us know. I am not certain what would be causing that behavior, testing locally I cannot make that happen. Will you please provide a bit of extra info? I think there may be a set of conditions that continue to cause that behavior.
If you can show me the block settings, that might help me to narrow down the cause. These are from the editor, so do not save the post after you get this information.
The settings used on the Services block.The contents of the editor, all blocks.
The composition of the service block.
And also the WordPress version, and other plugins. I am most specifically curious about the Gutenberg plugin, but others could also relate to this behavior.
Thank you,
Best regards
AnthonyHi Folks,
CoBlocks 3.1.9 was just released which includes a fix to an error condition with the Site Design extension. This should be unrelated to the ‘SSL’ errors reported earlier in the thread, but resolves an issue with Site Design regardless. If anyone else hasThe “coblocks-site-design” plugin has encountered an error and cannot be rendered.
message, this new version of CoBlocks may resolve the issue.
Best,
AnthonyForum: Plugins
In reply to: [Page Builder Gutenberg Blocks – CoBlocks] Unsure of ProblemHi @otb11,
Thank you for taking the time to make a report about this issue. It sounds like you may be experiencing multiple issues. Just released was CoBlocks 3.1.9 which has a fix to the Site Design extension for a few conditions where it might error. I advise giving 3.1.9 a try to see if it resolves that Site Design error you have. If not please let me know along with any console errors you might have in your browser console.
I do not know why you would have missing content, so I’d suggest trying this first and seeing the results.
Best,
AnthonyHi Folks,
Thank you for taking the time to make a report and to bump it as well. This is not one I can replicate its behavior. The lines indicated in the error message are related to network requests coming from the Google Fonts API and thus theunexpected eof while reading
is referring to the Fonts API call – in other words we can not modify their outputs.
Doing a Google search around for the error It does seem that this exact type of error with OpenSSL is reported across many software stacks. Everything looks to be indicating a configuration or version issue with OpenSSL. I would advise you to check with your SSL implementation. I suggest your host or server administrator would be next to check with.
Best,
AnthonyHi @scottfillmer,
Thank you for the update. I know that over time Core blocks have replaced many of the functionalities of CoBlocks, but not all. I see a single commonality between the errors you posted and the block attributes in the post-content you have provided. Lightbox is the attribute that sticks out to me. I see that relatively recently, WordPress has introduced its own ‘Lightbox’ that seems like it may be conflicting with the CoBlocks ‘Lightbox’.
Here is the work done on the WordPress side to add that functionality.
https://github.com/WordPress/gutenberg/pull/50373
This may be the related issue on the WordPress side that they are referencing but I am not positive.
https://github.com/Automattic/jetpack/issues/19496
I have created a bug report on the CoBlocks GitHub repository for our tracking. I hope that we can get into investigation and fix this at some point but it will require a lot of thought given the nature of the ‘closed ecosystem’ that WordPress.com uses.
https://github.com/godaddy-wordpress/coblocks/issues/2577
Best regards.Forum: Plugins
In reply to: [Page Builder Gutenberg Blocks – CoBlocks] conflict with The Events CalendarI had a thought about the nature of the error regarding passing by reference. It could potentially be related to PHP versions. Can you identify what version of PHP, WordPress, and CoBlocks you are running?
Forum: Plugins
In reply to: [Page Builder Gutenberg Blocks – CoBlocks] conflict with The Events CalendarHi @alwiggins,
I installed The Events Calendar plugin and added an event to test out the flow. I was not able to replicate the error on my end, unfortunately, so I am not sure how to replicate this behavior. I honestly am not sure what would be causing that error and the error is not very explicit. I find it strange that this error is pointing out core files from WordPress as well. Do you happen to have any other errors? Perhaps if you enable debug logging, you might catch or see additional errors?
Here are instructions for debug logging.
https://www.ads-software.com/documentation/article/debugging-in-wordpress/#wp_debug_log
Here is a test event that I put up.
https://njc.f0f.myftpupload.com/?post_type=tribe_events
Best regards.Feel free to remove any sensitive information if you feel that you should. I only want to see the code but by all means, protect your personal information.
Here in the thread is just a fine place. You can insert ‘code’ blocks using the blue ‘+’ or plus button. The code block should prevent the copy-pasted code from taking on additional formatting.
Hi?@scottfillmer,
That is a frustrating experience to be bounced back and forth. I’ve thought of something that may help us a bit more to diagnose the issue you are facing. You mentioned that the pages would not allow you to load the editor, but you were able to load the pages after disabling CoBlocks. I am curious if there is a combination of blocks or specific configurations that might be causing this. Perhaps if you were to disable CoBlocks for this purpose, then edit one of the error pages, and then copy and paste all of the blocks to us, that should give us the complete list of blocks and their respective attributes.
I am not sure what could cause that behavior but hoping there might be something in the block attributes that jumps out. In regards to the copy-paste, it may help to be in the ‘code editor’ view as can be seen in the lower right-hand corner of this screenshot.Best regards.
Hi @scottfillmer,
Thank you for the clarification about your hosting. My understanding is when using WP.com for hosting, that host uses a modified version of CoBlocks. I believe it uses a fork from the Open Source CoBlocks repository but it has been a few years since I have seen any movement on the fork. In this case, I would advise contacting WordPress.com support concerning that issue. Feel free to point this thread out to the team at WordPress.com as well.
I cannot pull anything of value from those errors on my end but I suspect the WP team may be able to. Any findings they have they can pass along to us if the need arises. I hope you find a suitable solution to this.
Best regards.Hi @scottfillmer,
Thanks for reaching out about this. I have not been able to replicate this and I do not know what could be causing this behavior. Is there any chance you could provide some error logs for this? It may require activating error logging and debug mode for WordPress. Also, I am very curious if you have browser console errors going on that may hint at the issue.
Browser Console – how to view
https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/console/console-debug-javascript#demo-page-javascript-error-reported-in-the-console-tool
Debug log documentation.
https://www.ads-software.com/documentation/article/debugging-in-wordpress/#wp_debug_log
If you could respond with any errors you find it may help us to identify the issue you are facing. It would also be helpful if you could identify some other software versions you are running but most important are the Console errors and Debug log.
PHP Version:
WordPress version:
CoBlocks version:
Best regards.Hi @alexhun1, I cannot replicate this behavior using CoBlocks 3.1.5. I’ve attempted to use a few different versions of WordPress and different themes but I cannot replicate that behavior. Can you advise on some software you are running that may be influencing that behavior?
Here are screenshots of the block preview in the editor.
What version of CoBlocks?
What version of WordPress?
What version of PHP?
Does this behavior occur while other plugins are running?
Best,
AnthonyHi @machepap , I did some testing using WP 6.2.2, CoBlocks 3.1.2, and the Bootstrap Basic4 theme. I attempted to use several carousel blocks on one page with columns set. The carousel reflects the same in the Editor and on the Published page regarding columns. Here are some images showing what I am talking about.
It makes me wonder if there may be a styling conflict with another plugin that may be causing the behavior in your report. For example, I think the Elementor plugin may have some style conflicts that we still hope to resolve.Editor Screen
Publish Page
It makes me wonder if you may have a misconfigured Carousel block. Notice the setting for Arrow Navigation for example. That may result in your missing arrow buttons.Carousel Settings
Forum: Plugins
In reply to: [Page Builder Gutenberg Blocks – CoBlocks] Fatal error on form submissionWe have confirmed the successful sending of our forms in our tests. The form functionality itself uses the wp_mail functionality to send mail. Essentially there is no custom configuration to send an email with the CoBlocks Form block, instead the Form block uses the built-in methods that WordPress has.
That said, it could be something with the email address set. View the screenshot below to see what I mean, there is an option to set the receiving email address.
It is also possible that the hosting provider is having some deliverability issues around sending to a specific email box. One example is that most shared hosting providers use shared email servers. A mail server can be impacted by bad actors, which then affect all of the users on the shared server/email server.
I do not know if that is the case, but it seems likely that there may be a deliverability issue occurring. I would recommend contacting your host and see if they can identify where the email is going. Another way to test if it is deliverable would be to use a separate email address altogether and see if it delivers as expected. For example, if you have agmail
address, using ayahoo
email the address would be a different domain that may not have the deliverability issue.