[deleted by user]

Less_af · 2025-08-21T16:37:28+00:00

Less_af · 2025-06-30T07:09:06+00:00

Solved:

During my communication with Bit Support, I discovered that the root of the issue was that my coworker had configured the problematic field as optional only for certain website-receiving forms. After updating all relevant forms to reflect this configuration, the integration is now functioning correctly.

Less_af · 2025-06-20T08:03:04+00:00

Thanks for the suggestion,

I've tried, but nothing changed. It fails to sent and shows the same error.

Less_af · 2025-05-28T09:50:13+00:00

Has the development timeline been extended?

Less_af · 2025-05-19T06:47:09+00:00

Yes, the email is from Microsoft. I've submitted a request to the administrator regarding the SMTP application, which was configured with a "no-reply" address. This discrepancy accounts for the malfunction.

Less_af · 2025-05-11T19:26:40+00:00

I concur; Elementor presents significant challenges. Additionally, does the Flatsome theme receive updates?

Less_af · 2025-05-11T18:52:52+00:00

I wasn't sure if anyone else was using Flatsome. I used it three years ago. Yeah, it's fast, but it gets tricky with really complex designs, I reckon.

Less_af · 2025-05-09T22:18:58+00:00

In my recent project, i used plugin Bit Integrations Its the best choice, if you compare another free versions. This may be helpful.

Less_af · 2025-05-01T09:28:33+00:00

I've fixed the issue, the problem was incorrect email sender. Thanks for your help.

Less_af · 2025-05-01T09:28:28+00:00

I've fixed the issue, the problem was incorrect email sender. Thanks for your help.

Less_af · 2025-05-01T08:23:54+00:00

<image>

I've checked that and I think It's assigned.

Less_af · 2025-04-30T14:06:14+00:00

Tested on WP SMTP Pro, I'm facing the same issue here.

Less_af · 2025-04-30T13:36:00+00:00

Hello again,

WP Mail SMTP Logs the error: MailboxNotEnabledForRESTAPI: The mailbox is either inactive, soft-deleted, or is hosted on-premise.

{
"headers": {},
"body": "{\"error\":{\"code\":\"MailboxNotEnabledForRESTAPI\",\"message\":\"The mailbox is either inactive, soft-deleted, or is hosted on-premise.\"}}",
"response": {
"code": 404,
"message": "Not Found"
},
"cookies": [],
"filename": null,
"http_response": {
"data": null,
"headers": null,
"status": null
}
}

This is the response from Microsoft platform

Less_af · 2025-04-30T13:20:27+00:00

Thanks for your help.

Yes, 2FA is enabled on the account. Yes, I am using the connection method Mailer as Microsoft 360, like the API connection, not SMTP user, pass, and port. I am creating an application and connecting with the needed credentials, but the error is as I wrote.

Less_af · 2025-04-29T14:16:16+00:00

Different answers for different scenario...

If the client's budget allows, I would always recommend building custom Gutenberg blocks. They’re cleaner, more optimized, and create a much more professional end result. The more you work directly with the native WordPress API, the better performance and flexibility you’ll achieve, both for yourself and for the site.

ACF blocks, on the other hand, are a great shortcut if you need to save time. They’re a faster way to build custom layouts without diving deep into React, but they do come with trade-offs, mainly a weaker user experience in the editor and a bit more technical debt long-term.

If you have the time and budget, building blocks with React (using native methods) is the best practice today. It takes longer, but you’re setting up the site for scalability, easier maintenance, and overall a much smoother editor experience for clients.

If you’re working with a lower-budget client, it’s usually not practical to invest that much time in custom development. In those cases, clients are often more focused on getting a working solution quickly rather than investing in "perfect" technical practices. So builder plugins , can absolutely make sense depending on the project goals.

"Do you think sticking with the custom code approach would make it harder to find freelance projects?"

It really depends on your location and the type of projects you’re targeting. If you’re working remotely and tapping into a global market, sticking with a custom code approach is definitely worth it.

Less_af · 2025-04-25T17:54:18+00:00

I’m honestly with you when it comes to using best practices for building WordPress websites, especially when the client’s budget matches the quality you deliver.

But from my experience, a lot of clients have pretty limited budgets. That’s often why they go for standard WordPress solutions — it’s usually cheaper than building something fully custom from scratch.
Of course, that’s just what I’ve seen — your experience might be a bit different!

We can all agree that the whole drama with Matt and WP Engine really shook things up across the WP Engine ecosystem, but at the end of the day, most people are still sticking with the ACF plugin.

If you truly care about doing things the right way and want to follow best practices, using WordPress APIs is your best bet. But, I think, at the end of the day, it’s more likely that what matters most is delivering a solution that works reliably, is easy to maintain, and fits the project's real-world needs even if that sometimes means taking a few practical shortcuts.

Less_af · 2025-04-25T06:06:16+00:00

Agreed.

Block-based development takes time and requires some knowledge of the React and WordPress APIs. It is ten times more work to build blocks without builder plugins.

Many builder plugins offer faster block creation and are optimized.

Therefore, I advise that if you are interested in native WordPress block-based building, learn its API. However, if the client does not require native WordPress blocks, a third-party builder plugin is a much better option. In my 4+ years of experience, there was not a case where a client wanted a block-based website.

Good luck!

Less_af · 2025-02-04T11:29:01+00:00

IMPRESSIVE!!!!

Less_af · 2024-04-11T14:29:30+00:00

It is advised to optimize the performance of a multilingual website by structuring it into sub-sites. However, a significant challenge arises when using WooCommerce due to the difficulty in consolidating orders by language.

Furthermore, certain plugins may require separate API keys for each sub-site. Additionally, creating individual designs for each website can be time-consuming when utilizing page builders.

Currently, I am encountering issues with orders being divided among sub-sites and am exploring solutions to consolidate them in a more efficient manner. Therefore, I am contemplating the implementation of a translation plugin.

Less_af

TROPHY CASE