Abhijit Nage

Hi @karlemilnikka and @jehnlemole ,

I apologize for the delay in our response.

We’d like to take a closer look at your specific situation to ensure we can resolve the issue. Could you please open a support ticket at this link: https://wpspectra.com/support/?

This will allow us to gather the necessary details to assist you further.

Thank you for your understanding, and have a nice day!

Best regards,

Abhijit Nage

Hi @karlemilnikka ,

Regarding the Astra theme’s autoloaded settings row, I want to assure you that we are currently evaluating this issue.

Our team is reviewing the autoloaded options and assessing how we can optimize it further. We’ll keep you updated on our progress, and once we have a clear resolution, we’ll provide further guidance.

In the meantime, if you have any other questions or need additional assistance with Spectra, feel free to reach out.

Best regards,

Abhijit Nage

Hi @karlemilnikka and @jehnlemole ,

With the latest release (2.16.1), we’ve implemented a script that automatically deletes all ast-block-templates_data entries from the database after the update. However, if you are still seeing these entries in your database, you can safely delete them manually. You can search your database for any options starting with ast-block-templates_data and ast-block-templates-spectra-common-styles and remove them.

Additionally, regarding the ast-block-templates-spectra-common-styles entry, in the previous release, we’ve stopped storing this data in the database. Instead, we’re now generating a JSON file and storing it in the uploads folder. If you’re still seeing this option in your database, it’s likely an old entry, and you can safely delete it manually.

Instructions to Remove Autoloaded Data:

• Update the latest version of Spectra (2.16.1): On updating to this version, the autoloaded ast-block-templates_data options should be automatically cleared out. If you have previously uninstalled Spectra, then just install the latest version of Spectra.
• Manual deletion (if needed): If the entries are still present after the update, you can manually remove any options in the database starting with ast-block-templates_data and ast-block-templates-spectra-common-styles.

If you encounter any difficulties with the cleanup or have further questions, please feel free to reach out, and we’ll be happy to assist you.

Best regards,

Abhijit Nage

• This reply was modified 1 month, 1 week ago by Abhijit Nage.

Hi @karlemilnikka ,

Thank you for following up, and I truly appreciate your patience throughout this process.

My apologies if my phrasing was incorrect. I would like to clarify on what I meant when I said that we will release it in the Spectra release after the next version (2.16.0).

At that time, we had frozen the 2.16.0 package for release while we were working on resolving the auto-cleanup issue in the library. What I meant to say was that we will release it after the 2.16.0 release.

That being said, I’d like to inform you that we have now addressed the cleanup, and it has been included as part of today’s 2.16.1 hotfix release.

Please feel free to reach out if you have any further questions, and thank you again for your understanding.

Best regards,

Abhijit Nage

Hi @karlemilnikka ,

I’m Abhijit, from Spectra development team.

Thank you for following up, and we appreciate your patience.

I wanted to provide an update on the autoload issue. In version 2.15.2, we made updates to the GT library, which resolved most of the autoload problems. Additionally, autoload entries from pages and kits are now automatically removed once they’re no longer needed.

While a recent audit found that the issue still exists with block patterns, the problem related to kits and pages has been resolved. We’ll be including a cleanup fix for the remaining ast_block_templates_data-XX entries in the Spectra release after the next version (2.16.0).

In the meantime, you can safely delete any options in your database that start with ast_block_templates_data-.

Thank you again for your understanding, and we’re committed to fully resolving this issue as soon as possible.

Best regards,

Abhijit Nage

Hello @erikmolenaar ,

Thank you for bringing this to our attention. We have identified the issue and created a story for our development team to address it. We will make sure to fix this in an upcoming release to prevent any further database clutter.

Your feedback is valuable, and we really appreciate your help in improving Spectra.

Best regards,

Abhijit Nage

Hello @sterrivel

So sorry for the trouble.

The problem you’re describing is not yet on our list of “known issues”.

Could you please explain more about the issue? What exactly breaking on mobile? Some screenshot or step to replicate the issue will be helpful.

Also you mention you have roll back to the previous version 3.9. It seems you rolled back theme previous version. Is that right?

Looking forward to resolving your issue.

Thank you for your patience.

Hello?@elias69 ,

So sorry for the trouble.

The problem you’re describing is not yet on our list of “known issues”.

Could you kindly get in touch with us via our helpdesk on our website? This will allow our developers to take a closer look and find a solution for you.

Please attach some screenshots and more details about the issue in the ticket.

Looking forward to resolving your issue.

Thank you for your patience.

Hello @takumi412,

Thanks for reaching out to us!

Yes for now could you please use below filter in order to show limited Chinese or japanese word in excerpt of post grid?

add_filter('uagb_single_post_excerpt_grid', function( $excerpt, $id, $attr ) { return custom_post_content(10); },10, 3 );
  
function custom_post_content($limit) {
	$cur_lang = get_bloginfo("language");
	if ($cur_lang == 'zh-TW') {
		$excerpt = strip_tags(get_the_excerpt());
		$excerpt = mb_substr($excerpt, 0, $limit);
	  }elseif ($cur_lang == 'en-US') {
		$excerpt = strip_tags(get_the_excerpt());
		$excerpt = mb_substr($excerpt, 0, $limit);
	  }
	return $excerpt;
}

Above code result will look like this – https://share.getcloudapp.com/jkumopoB

Further will add a task for the same in our to-do list. And assign to concern developer for fix. We will surely improve this in our upcomming updates.

I hope you understand.

Regards,
Abhijit

Hello @droyed,

I will surely convey your feedback to our concerned developers. We are always keen to listen to our customers and to receive their feedback. This is the best way to improve our products and services and maintain our client’s satisfaction. ??

I’ll put forward your thought about this to our team and if feasible we will try to improve the scenario in our future updates.

If you have any further queries, please don’t hesitate to contact us.

Regards,
Abhijit

Hi @allanext,

We have replied to your ticket ID – 126919.

Could you please check it once?

Please check screencast to know how tabs anchor work.

I hope you understand.

• This reply was modified 2 years, 11 months ago by Abhijit Nage.

Hello @yaphhakimi,

We are really happy to hear about your experience with the plugin.

And thank you for taking the time to leave a review. We appreciate it!

Have a great day ahead : )

Hello @droyed,

I would suggest a second one. In that, you can use both Post grids to show posts on different pages, and also on the same page, you can use our FAQ block.

I hope it helps

Regards
Abhijit

Hello @pilam,

Thanks for reaching out to us!

Unfortunately, as of now, we have not added this feature yet. But I would love to take this as a suggestion. I have added this to our task list. Our team will work on it and we’ll try to add this feature in our future release.

We really appreciate your efforts and patience.

Regards,
Abhijit

Hello @mohsenpazhoohiyani,

Thanks for reaching out to us!

Unfortunately, as of now, Ultimate Addons for Gutenberg does not support AMP yet. However, it is on our to-do list. We’ll try to improve the scenario in our future updates.

I hope you understand.

Regards
Abhijit