opentype

In the Pages template your database uses for the “record view”. It isn’t. It’s an application of the Twitter code. You can’t just paste the Twitter code. It’s just an example. The fields need to be populated with the dynamic content from the database record. Also, don’t just copy my code above. That’s also just an example. My Pages template include Twitter card support. You don’t need to do anything else than add your Twitter handle to the template.

If the iFrames need to be only used by admins, then the mentioned method of turning on HTML in posts and allowing the iFrame base is the way to go. If the regular members also should be able to add iFrames, then in addition to allowing the iFrame base, you can create a new editor button for the specific external service. You can then safely let users paste a URL or a media ID and the button creates the embedding HTML snippet.

In the future, please ask first to clarify what the intended functionality is and how one can set it up. What you describe here isn’t true and it is not helpful to make false statements in the support topic and cause unnecessary confusion among existing and future customers. There is no sub-category view. There is a front page view and a listing view. Both have their own settings. So if you visit a (sub-) category, you can of course have clickable thumbnail (resolution) images there, if both are options are turned on for the listing view and you make sure that you are using the latest templates. The other two points are a matter of opinion. You are free to have yours, but that doesn’t mean there is a lack of “refinement for a paid script” on my part.

Please be more specific. What does “doesn’t work” mean exactly?

I uploaded version 1.1.

In will be like this in the next update. Feel free to apply that already:

A block template is included, but it is only meant for the sidebar. The full grid view only comes with the database templates.

It checks for the existence of the Twitter handle AND the existence of a Record Image. If both are valid, the meta tags should be generated for the specific article page.

There is additional padding for these 3 statements: #elCmsPageWrap article.ipsContained #elCmsPageWrap .ipsClearfix section.ipsType_normal … which adds up in this way. There isn’t much more help I can offer but to tell you that. It’s the styling of your theme, as expected.

I need to see this on a live site to see where the space is coming from. Its probably from your theme, not from my template.

Yes, I will probably make that a default in the next update.

Sounds like a case for customization for a specific site. Since there is no “category image field” or anything like that which I could call from the template, it’s not something I can support in a “general use template”.

@Himadri Goswami By the way: please also make the CSS change described here. Your library section is affected by this problem.

Not at the moment. I might add that in the future if people really need that.

Not sure what you mean by “custom blogs”. I see a feature badge on the article front page and in the People listing view. So the badge seems to work as expected. The templates are unrelated to specific editor content or custom fields. If you put videos in your articles or add custom database fields to your database, that will work just as with the stock record view template.

Okay, I just tested it locally. This is what it would look like: If anyone needs this sub category view on listing templates quickly, feel free to send me temporary admin data and I install this template change on your site so you can use it and I can test it on a live site.

If you don’t use my templates for record display, then article sharing problems on social media can’t have anything to do with my templates. I am happy to check it out nevertheless, but you need to give me a public link. Those pixelated images tell me nothing. I see. Yeah, that comes from my CSS. Go to your custom CSS and find: .cCmsRecord_image { float:right; margin:8px 0 30px 30px; } Change it to: .SG_record_right .cCmsRecord_image { float:right; margin:8px 0 30px 30px; } Thanks for reporting. I will include that change in the next upgrade.

Understood. I also answered that here recently.

Absolutely! Please check the installation PDF. Accessing the settings is described there.

Pages → [Your Database] → Fields → Permissions Make sure the users who should add/edit articles have permission to edit all the fields. It appears, once you set the “Index mode” of the database to “show records like articles” in the database settings.

Regarding the boxes: The colors are all inherited from your theme. If your theme designer has made ipsAreaBackground_light transparent or identical to the background, then this is what the SuperGrid template will use as well. In order to change that you would either have to change your theme colors or give each SuperGrid box a specific background color (in the custom.css) to only affect the Pages template. .SG_card { background-color:#333; } The overflowing text is a problem of the post itself. You pasted rich-text with tons of styling in there, including a width statement which forces a width of 1007px. You should clean up the post and only paste plain text and it will be resolved. It has nothing to do with my template.

Then you need to to make the style declaration more specific. Like: .SG_card a { color:#555; }

Those are regular H2 headlines using the default link color of your theme. So whatever your link color in your theme is, the SuperGrid templates will use.

I see. Yeah, the template is calling the default category row output at that point. I will have to do some testing to see if I can work around that without creating other problems. If it works, I will put it in the next update. It wouldn’t change much though. Basically just removing the icon and adding the Grid colors. So it’s more something for the to-do list, than for an immediate fix.

Probably. I am open to suggestions. If you like the look of a certain WordPress theme and want something like that in Pages or of you have certain design problems with your Pages database … Let me know. I can check if there is a solution I can build. Make sure the sub-category itself is set to have the listing view inherited from the parent container.