You can emebed any video content into any website using normal HTML.

be aware QuickTime is no longer secure on Windows and should not be used on ANY Windows-based machine as major security risk. Apple has abandoned QuickTime on Windows. Any Quicktime video should be converted to MP4.

See the WordPress codex/docs for how WP supports video natively:
https://codex.wordpress.org/Video_Shortcode

Most modern browsers, and WordPress support these formats:
‘mp4’, ‘m4v’, ‘webm’, ‘ogv’, ‘wmv’, ‘flv’

note with some things, you do need the explicit http or https in the URLs; shouldn’t be the case but I’ve run into this issue a few times

src="http://www.pelikan.hu/ etc.

Worth trying that 🙂

also double check the quote marks are " inch marks and not curly quotes.

• This reply was modified 9 years by simchris.

No, right answer: the whole idea is to move away from “theme shortcodes” and use agnostic shortcodes not tied to themes. Theme shortcodes based on CSS have nothing to do with VC. Speaking as a 22 year wevdev, and 12 year WordPress dev.

Again – plenty of very simple plugins which allow you to add custom shortcodes to the editor, for things like the typical Bootstrap style buttons, wells, panels, alert boxes, etc. — all these plugins do is add some additional CSS for you for the styles you wish.

Frankly, if you learn to code with WP, you can even very simply add your own CSS shortcodes and functions in the functions.php file. There are even online shortcode generators you can use, like so: https://generatewp.com/shortcodes/

However – to make my point:
For example, this one has over 600,000 installs; you could have installed it faster than arguing with me on how to resolve your query:
https://wordpress.org/plugins/shortcodes-ultimate/

(( I don’t work here and do not speak for TagDiv ))

• This reply was modified 9 years by simchris.

Theme does not have security issues.

however, are you running latest version of WordPress? ALL older versions can be hacked.

Have you removed all old un-used themes and plugins?

Have you done the recommended security hardening recommended in the WordPress codex/docs (wordpress.org)?

Scan your site with Securi site scanner to see what issues you might have.

Then do CLEAN install of WordPress, all plugins and all theme files ASAP.

Lots of shortcode plugins out there.

Most themes are no longer adding excessive shortcodes as these will break and “be gone” if you switch themes in future as they are tied to theme CSS.

Check out all the awesome shortcode plugins in the WP plugin repo.

That is what most of us do. No need to “wait” — just go do it 🙂

You can request that from Themeforest — see the help on TF website for requesting refunds.

I use Auto Post Thumbnail Pro; which sets the featured image, and then the featured image gets placed onto page with a template supporting use of featured image as primary photo on post.

Which dynamic widget plugin?

Many form plugins work with theme; many require either

a) create form; insert shortcode for form onto a ‘page’

b) create custom page template and hard code form into that

most work with ‘a’ method, and always have.

I don’t think it’s updated to work with 7.1.x only 7.0x

You can’t have pages and categories with the same name / slug if using pretty permalinks. How can it send a request to two diff pages with same name?

So make sure the ‘slug’ is notably different when editing the post.

You cannot have

page = How-to-Order
cat = How-to-Order

you need to do something like

cat = how-to-order
page = how-to-order-our-services

or similar.

Chris

Also, ensure you have gzip/deflate properly setup on server and possibly via your htaccess file.

This compresses the files when sent to browser by 80% to make things very speedy.

Test site with GTmetrix.com to see if you need to do that.

Skype is not a social network.

However, google great resource for learning stuff…
https://support.skype.com/en/faq/FA99/how-do-i-add-contact-me-buttons-and-skype-uri-links-to-my-website-or-app

A.. file is compressed if you have gzip/deflate properly setup on your server.
B.. you can minify the css file once done making any customizations to it.

Generally, the AMP version has no relation to the main theme as the AMP endpoint is highly mobile optimized and doesn’t support any of the theme features, so kind of pointless to have as “part of the theme.”

But we all have our own thoughts on this.

What if TagDiv abandons the theme on your 100,000 page site, and no longer works with PHP 7.5? You’d need to suddenly change to an agnostic plugin. if you had been using agnostic plugin originally, it would work regardless of “theme.” I prefer that “separate” function, personally, especially if it gets added into something like http/2 as a feature.

I’d like a flying car, too, but not going to hold my breath 🙂

I’m out!

• This reply was modified 9 years by simchris.

I guess my point was, theme devs not going to make the theme mobile plugin setup for AMP, as this would introduce giant amount of support for people who don’t understand AMP or how it works.

For example the mobile plugin could support non https, and support javascript, and various things which AMP does not support, ad units, TagDiv API, speed booster hooks, etc.

It would be NICE if they had an AMP plugin that works like the mobile plugin, as separate paid product, perhaps, which could replace the one included with theme with specific guidelines on what it does and can never do. Two totally different things.

Making ONE mobile plugin for theme that worked for both mobile/noAMP and mobile/AMP would add huge amount of code bloat, also possible issues with adding the AMP end-points and hooks and all sorts of bizarro potential issues with folks who can’t even clear their caching when updating.

“In a perfect world…” sure, would be nice. But unlikely to happen anytime soon.

Frankly, I believe the “back end” skunkworks plan is more focused on developing a replacement for Visual Composer for their “ION” version and doing sideways dev on that which can be sold outside of ThemeForest as traditional foundry method (“direct sale”).

I got what you were saying about “wouldn’t it be nice if …” — I was just pointing out wasn’t going to happen based on working with them for 3+ years here.

The support overhead for that would be insurmountable from a business case standpoint. Look at all the issues with Facebook (“why doesn’t my photo show up…” or “why isn’t my views incrementing…” “why do I need a Facebook account to use the FB widget …” etc.). So, experienced devs already moving on making their own solution based on the available tools; newbies already confused by what AMP is, and unlikely to get the issues with search/replace of inline styles, ad unit custom inserts, etc.

It’s awesome we have so many active folk here actually “into” this stuff.

My opinions are only my own, so take all with grain of salt — sure you were doing that anyway 😉

But again, to get on with your life you really should consider this the way forward:

a) desktop > theme CSS (main URL)
b-1) mobile > theme CSS responsive (main URL)
b-2) mobile > theme plugin/CSS mobile (optional) with custom settings (main URL)
c) mobile > AMP compatible > AMP plugin + custom template (AMP endpoint)

You can only have 3 of the 4 options as it stands.
In our case we do a, b-1, c.

What you were wanting was a, b-2 – where b-2 has multi-thread option based on visitor including redirect to AMP endpoint vs normal URL.

Betcha box of gingerbread cookies you will have an eternal wait on that!

Are they being added to your sitemap by your sitemap software? Or, tracking software connected to Google Analytics counting those as views?

That kind of thing not theme related.

You should upload/install via FTP, as some servers have varied permission settings.

See theme docs regarding bundled version of VC with the theme; it’s updated only when theme updated. Or, you can buy your own separate license if you need support from WPbakery.

This is the nature of moving to https — all your URLs are now different URLs.

The TagDiv plugin only connects to your FB account/app to “get the info” — so, the new pages with NEW URL have no shares, so that is what is shown.

You will need to Google various solutions for this issue, search forum for past issues and possible solutions.

Theme devs can’t create hack for you, as not theme related. This is how FB works — each URL is unique.

Yes, https is more important than tracking who liked your pages – nobody except you really cares about that. The average user does not care, which is why we removed that element from all our news portals in 2014.

So, likely good to go scouting Google for solutions on how to address this, the FB support forum, etc.

Perhaps a kind soul who already dealt with this will chime in as I’ve done — we chose to just abandon the likes count, as not relevant to the ‘actual’ content we create. We prefer ‘shares’ over ‘likes.’

Anyway — food for thought (I don’t work here.)

Theme devs can’t fix it, as nothing to fix. Plugin is doing what it is designed to do; it’s just the data has changed. So, it can’t count a URL that doesn’t exist.

I think some people hacked it to feed the non https to the counter, vs the http — but you will need to look up that hack if still mentioned in forum. Sorry.

Theme doesn’t manage SSL or Facebook counts, technically.

So, when you change your URL, it’s no longer the same URL, as treated by FB. There are some hacks out there, which generally need to be done in the main functions.php file.

Also, you need to ensure
a) you have set the https url explicitly in your wp-config.php file
b) done a search/replace for http/your site to https/your site in yout MySQL dbase
c) setup a redirect in your htacess file for all http requests to > https

Whatever hack you use aside from the above “required” stuff for moving to https, be aware it may not always work as you are tricking FB into seeing the old link as the new link, when technically it’s not the same URL.

Much like adding the new site to your Google search console, they stupidly consider it a new site, and does not replace the original in your search console; also note inbound links will show different, and your indexing may change for up to 3 months with the shift.

It’s very much worth doing and should be considered required to be https these days, but you have run into just one of the many issues in the ‘move.’

Try putting the function into the *main* theme functions file. This is one of the many reasons I never use child themes; makes this kind of thing notably trickier as the child theme is essentially a CSS redirect to over-ride the main theme.

We’re not having the issue on our sites.

To be validated as AMP content, it must pass Google’s AMP validation, and then added to separate “map” for mobile users in SERPS, and then they are presented *only* the AMP formatted version and NO other version. Also they get a lightning bolt element in SERPS to identify it’s AMP formatted and hence “speedy.”

The only reason we’re trying to explain to you how it actually works as some of us have actually been doing it for a year and a half.

You can’t make a page identical to your desktop version for AMP as that defeats the purpose of the mobile friendly AMP framework. It’s supposed to be “lean and mean.”

If you want a desktop experience on mobile, it can’t be an AMP version.

But you likely need to experiment with this yourself to see “what actually happens” vs the theoretical idea you have in your head.

Spend some time on the Google AMP docs for more information.

Anyway — just food for thought.

Theme devs not going to add built-in support, likely, for many of the reasons already covered here by everybody who has already been down this road and are “doing it right now.”

AMP needs custom classes, compliant post meta code, special ad unit setup, custom hooks for plugins, no use of javascript stuff, https-only elements, etc., etc.

I’m out !

No. The AMP plugin replaces the mobile theme with the AMP version, where portions of the content get cached on Google servers under high demand as a CDN structure.

If you plan on using AMP as your main mobile element, then the theme mobile support is only used for those instances where AMP is not used.

You can modify the AMP templates however you wish.

Desktop => theme template
Mobile => theme template/mobile (optional)
Mobile AMP => AMP template via plugin

AMP has very specific requirements outside the scope of the theme.

For example, WordPress allowed you to use the visual editor to add <p style="center"> which is bad HTML in modern usage. This will cause AMP validation to fail.

Theme authors cannot spend the time to support the ins/outs of AMP which change over time, and for which there would be unreasonable amount of support time provided to those who don’t understand how WP works, how AMP works, and can’t RTFM.

It ONLY makes sense to use an “agnostic” plugin like the one from Automattic (we have been using it since Nov 2015). This puts the brunt of development/compliance on the backs of WordPress devs and not theme devs, since it gets used for all the tier 1 “VIP” WordPress sites like TIME magazine, etc.

Really — anybody who wants to implement AMP should look into using the AMP plugin, then learn to tweak per the requirements as that is “best” way to go to save yourself major headaches, pain, suffering, and torment!

It’s neither economically feasible nor support-smart to build entire AMP support into the theme, which is already provided by the plugin.

(( I don’t work here. ))

Of course, that being said —
I did have to do that on a non-TD theme we use for one of our ecommerce solutions, where the method used to put featured block on front page was using “blah-ad_blah” … and so ad filters in browers would show blank boxes on front page of store thinking they were “ads” — we had to do a search/replace in the theme (I think we used either TextPad 5 or Dreamweaver) — I mentioned it to the theme foundry (a major foundry …); i still don’t think they’ve fixed that as they did it in *all* their themes. Had to fix all the “ad” classes to “neo” short for our company trademark and all that. Works fine. But — we tested the heck out of that before customer every saw it!

My lesson from THAT was not to us “ad” in any classes 😉