To add some context – I actually dont even need the pages, i JUST need the Cloud Templates.
Just to add to my last message, I would like to know precisely where the cloudtemplates are stored.
In the database? In some folder?
Can you tell me more about the copy paste method?
Where are the cloud templates stored on the site?
I dont think you understood my requirement.
On the post details page (rendered via the single post template from the cloud), I simply want to show the video link I added to the featured video field.
Pleasea advise how this can be achieved.
.
-
This reply was modified 8 months by
vikasnangia.
Hi there,
Can you please let us know a resolution date please?
There is a difference between Cloud Templates not supporting custom post types, and your theme not supporting custom post types.
How can we make custom post types work with your theme, if we decide not to use Cloud Templates?
For our Knowledge base we are using a plugin called BetterDocs.
https://wordpress.org/plugins/betterdocs/
The issue is that your theme does not work with custom taxonomies and custom post types. This is a huge problem as your theme does not work with anything else except default taxonomies and post types.
Found the issue. The offset was supposed to be set to BLANK not 0.
We have had to deactivate your mobile theme. After removing the mobile theme plugin see below :
Home page: https://www.appmysite.com/blog/
Image sizes on mobile: 636×392 and 150×84
Category page: https://www.appmysite.com/blog/category/mobile-app-builder/
Image sizes on mobile: 636×392 and 150×84
Why are 2 sizes being loaded on both the above page types? Are these the expected sizes?
To add to my last message, it appers that we’re able to configire the image size for category pages via the cloud templates section, but what about the mobile site theme settings?
Where is the setting that allows us to choose what image size to show on the mobile site theme? Currently it is defaulting to show 1536×864 on the mobile site category listing page.
“USE LOADING ANIMATION IMAGE” is set to off
So basically you are saying that we need to set the font for EVERY element, manually?
We’ve made sure we’re running the latest versions of all plugins and themes. All caches cleared etc.
Once again, you seem to be sending me references to images that are in the BODY of the post, whereas we’re asking you specifically about the FEATURED image which does NOT appear in the body of the post.
The AMP plugin had suppressed your divtag plugins. This was causing the issue.
Resolved now.
-
This reply was modified 4 years by
vikasnangia.
Hi there,
We have already set the color theme, which is why it is correctly displayed on the Home, Category, Tag screen. We did his via Theme Panel -> Mobile Theme -> Theme Color.
However, it is NOT displaying as expected on the Post Details screen. Here is the screenshot again. https://imgur.com/a/lPwiE0M.
It doesn’t make sense that we should need to look anywhere else, or at any other setting. Once we activate the mobile theme + amp, and set our colors for the Mobile Theme -> Theme colors , no other settings should be in consideration on the mobile site, and yet the header colors are not referring to the mobile theme settings.
This appears to be a bug.
This unfortunately is a deal breaker. Is this on your roadmap?
How can we modify the view of the “standard template” to match that of the other cloud templates?
Hi,
1. GENERAL MODAL IMAGE is set to OFF in the general post settings. https://www.screencast.com/t/8qraORSbx
2. My original question was in reference to feature images. This setting (https://imgur.com/MWdVYT7) does not appear for featured images.
So basically, both are off and yet the featured image is still clickable on the mobile, but not on the desktop.
Please help.
Just to add to my last response, the ARTICLE DISPLAY VIEW appears empty for all. Any idea why?
Have a look at this . As you can see, the first 2 images are the background and header colors of the home, categories, tags pages.
The second 2 images have colors are of the blog details page.
Never mind. Smush plugin had a setting that was conflicting.
REsolved now.