All Activity

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Nomor Whatsapp..? untuk menghubungi Tokopedia Seller adalah Chat +62.855.1212.305.) Anda bisa juga menggunakan nomor ini untuk mendapatkan bantuan Tokopedia..

Problem: Pterodactyl game eggs occasionally have the below problem The setFields() method in /app/models/services.php doesn't handle duplicate field keys in the input array. When modules or package configurations pass duplicate service fields (same key), the method attempts to insert multiple records with the same service_id + key combination, causing a primary key constraint violation: Root Cause: In line ~4165, the method loops through $vars and calls addField() for each entry without checking for duplicate keys. If $vars contains multiple entries with the same key, multiple INSERT statements are executed for the same service_id + key, violating the primary key constraint. Solution: Add deduplication logic before processing the fields array. Here's the diff that fixed the problem and stopped white redirect pages from occurring: Benefits of this fix: 1. Prevents crashes: Eliminates primary key constraint violations 2. Maintains functionality: If duplicates exist, keeps the last occurrence (allows intentional overriding) 3. Backward compatible: No API changes, same input/output behavior 4. Future-proof: Protects against any module/package that might pass duplicate fields Affected scenarios: • Custom modules that generate duplicate service fields • Package configurations with conflicting field definitions • Third-party integrations (like Pterodactyl) with complex field mappings

Sorry I did forget to add - that even though the redirect goes to a blank white page the pterodactyl integration still works and it will create a server based on the order. Its just confusing and unprofessional looking that you just get taken to this blank white page.

Hey guys, Pretty new to Blesta but I've got it working with pterodactyl at the moment and I'm having this issue that appears to be with most eggs I've tried where you place an order for them and the redirect after activating/ordering the service goes to a blank white page. Is this some weird PHP issue? The logs aren't showing any errors so I don't really have much to go off at the moment to try and troubleshoot it. Any help would be appreciated, cheers!

I'm not sure what you mean by not seeing a checkbox option. If you created a checkbox option and it does not appear, please post a screenshot of it.

Thanks for your response, is it possible I do not see this checkbox option?

Your config option needs to have at least "Client can Add" checked, or the option will not appear. I don't know why you have {configoptions.extra_backups} in that "Database Limit (optional)" field, but I'm pretty sure that should not be there. You get an error because it's supposed to be a number. Backups and database limits are 2 separate things.

A quick note that we do not frequent the forums, but the theme is updated frequently. We're currently on version 1.3.2, which supports Blesta 5.12.0. If you need more information on our theme, it's best to visit our website!

Hello, When I try to add a configurable option and I fill this in the module section: {configoptions.backups} I get an error that it has to be a number, how do I fix this?

Sounds good. Disabled PayPal Payments Standard, and Enabled PayPal Checkout, which I hope adds Venmo as a payment option. There is a small type-o in the doc https://docs.blesta.com/display/user/PayPal+Checkout After the Enter the details provided by PayPal Checkout section, right above the box that say's API Fields. It has "When finished, click "Update Settings" to save the details. You have successfully installed and configured PayPal Payments Standard!" lol

PayPal Checkout is newer and better than PayPal Payments Standard. If you have subscriptions from another billing system, then you'll need to redirect those IPN requests and you should add mapping for those within the gateway in Blesta. See https://docs.blesta.com/display/user/PayPal+Payments+Standard#PayPalPaymentsStandard-CommonIssues for more on doing a redirect. Note that PayPal Checkout IPN calls can interfere with PayPal Payments Standard, per the alert at https://docs.blesta.com/display/user/PayPal+Checkout It's generally a good idea not to use both.

We used PayPal Payments Standard with another billing system, should we continue using that or switch over to PayPal Checkout? Are there any benefits, I do see that Checkout allows for Venmo usage. Which is a plus. Thanks

Blesta's discord. We do not have any official discord for our themes.

HI, I've got two issues with the Namesilo module. I am running Blesta 5.12 and Namesilo 3.4.4. The issue was present on Blesta 5.11 as well. 1. I have imported some TLD's and they are available in the order form and prices are synced. When doing a search, for example: testdomain776655 it will return .co.uk as available, but it will not return any result for .com neither available nor unavailable. Looking in the module logs I can see the request being sent and the response indicates available for both. Response for .co.uk (I've removed the email address from the responses): https://www.namesilo.com/api/checkRegisterAvailability (REMOVED) O:8:"stdClass":3:{s:4:"code";s:3:"300";s:6:"detail";s:7:"success";s:9:"available";O:8:"stdClass":1:{s:6:"domain";s:22:"testdomain776655.co.uk";}} Response for .com: https://www.namesilo.com/api/checkRegisterAvailability (REMOVED) O:8:"stdClass":3:{s:4:"code";s:3:"300";s:6:"detail";s:7:"success";s:9:"available";O:8:"stdClass":1:{s:6:"domain";s:20:"testdomain776655.com";}} 2. The second issue is that I have deleted a number of TLD's that I don't want to sell, this was done in Tools -> Domain Options -> tick the ones I don't want and do a bulk delete. None of the deleted domains had any registrations against them. When a customer goes to the order form the deleted TLD's are still listed. Any help would be super appreciated. Tobey

Could you please update the composer packages: the "egulias/email-validator" and "psr/log"? When I tried to send an email using the Adyen payment system, it failed. I have to update the 'egulias/email-validator' and 'psr/log' with every new Blesta version, and it works fine.