lechon

@qtwrk

Hi,

Thanks for the explanation and feedback, I understand now.

Cheers!

@qtwrk

Hi,

This is the actual description your plugin gives on this:

“Specify the maximum size in megabytes for combined files. Larger numbers will generate fewer files, which is better for achieving higher page scores, but can cause heavy memory usage. Recommended value: 2”

You said “It’s not about “memory usage in this case”, but your plugin says “can cause heavy memory usage”, so I am confuse here.

So does this mean that the Recommended value: 2 is the same for a share hosting as well for a dedicated server, and a value of for example 3 or 4 can break a site no matter what the environment is?

Regards,

Hi @vaakash

Many thanks for the reply and feedback.

Regards,

Hi @vaakash

While we were waiting for the client to give us some feedback we discovered how we could make it work.

Like we said before, every shortcode in our library worked except for Shortcoder.

We noticed that all of the working shortcodes that we have, none of them uses ” ” double quotations inside the brackets [ ], unlike Shortcoder where it does, like for example [sc name=”myvideo”].

Removing the double quotes from Shortcoder does the trick, [sc name=myvideo], the code works in custom fields on Classic editor as well in Gutenberg with no issues.

The code also works using only single quotes [sc name=’myvideo’] and even it works when parameters are present in the shortcode like [sc name=’myvideo’ id=’123456′].

So what breaks the generated shortcode from Shortcoder is the double quotes inside a custom field.

With this said, the only way we are able to use Shortcoder is by editing manually the shortcode generated by Shortcoder in “Insert Shortcode to Editor” from double quotes to single quotes or no quotes at all. I guess we are Ok with this, but it’s a shame to loose this feature, as it’s handy.

Our question to you is, Is it OK to use your shorcodes without the double quotes and use single quotes or not quotes at all?
The reason we ask, is that we want to make sure that by doing this we are not opening a security hole somewhere, or futures updates to the plugin does not break the functionality on the shorcodes already embedded.

Regards,

Hi @vaakash

Thanks for reaching out to us on this.

Let me check with the client to make sure this is OK.

Regards,

Hi @vaakash
We don’t have a custom field plugin.

This is not the case with all of the existing shortcodes we have, they work fine on both Gutenberg and Classic using custom fields.

We really don’t understand why all of the other shortcodes we have work.

Actually your shortcode works on Gutemberg perfectly. It also works with any random sample shortcode like the one you provided on Gutenberg. Screen shot below:

View post on imgur.com

I would completely understand if your shortcode did not work at all in custom fields, but it actually does, it just for some reason it can not keep the full name in classic editor.

Hi @vaakash
it’s not a plugin, that is the name we gave the custom field.

@vaakash

Many thanks for your quick reply.

I am not the developer of this plugin, but I am not sure what you mean by NSFW (not safe for work) This is usually a term use for not suitable for work: used in an email or other electronic communication as a warning that it contains or links to pornographic, offensive, or other content unsuitable for viewing at work or in public places.

In any case…
You need to disable in the plugin settings “Enable Schema.org structured data markup for search engines”. This is not needed if you are already using an SEO plugin.

Other than this, this plugin works just fine, I have been using it for years.

@qtwrk

Hi,

It’s working again.

Many thanks,

Cheers!

@sandygarrido

Hi,
I am not seeing any errors on the console.

I have disabled every single plugin and nothing works.

Redirection is the only one showing this “jQuery Migrate Helper — Warnings encountered”

@qtwrk

Hi
The tool bars came back all of the sudden, now it seems to work. There were no errors on console anywhere. Just weird!

@johnny5

Thanks for the quick feedback.

Cheers

@qtwrk

I understand…

Thanks for the feedback.

Regards.

Hello @qtwrk

That worked!
Thank you very much!

Cheers!