fluiditystudio

I’m having the same issue. I just installed the plugin and then tried adding my API keys from google and went to save. I was then presented with a 404 error on the front-end of the website.

Thank you for the link to this other version. However, I’m still having the same issue. WP Debug doesn’t show any errors and I cannot figure out exactly where the error is coming from. Browser output error is below:

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

I figured out my issue. It was some code that was apparently no longer valid with settings that changed within the events calendar plugin itself. I removed that old code and updated the settings and it works.

Here is the code I was using that I removed:

remove_action( ‘tribe_events_single_event_after_the_meta’, array( Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance(), ‘front_end_tickets_form’ ), 5 );
// Place the form in the new location (after the content).
add_action( ‘tribe_events_single_event_before_the_content’, array( Tribe__Tickets_Plus__Commerce__WooCommerce__Main::get_instance(), ‘front_end_tickets_form’ ), 5 );

Having the same issue as well. Any progress on figuring this out?

That is not actually what I was referring to. I ended up placing the call to check if the license was active into a function that ran when WordPress update check runs. This eliminated the constant calls back to my site.

To clarify this further, this is the the code within the plugin that checks back to my website to make sure that the key is still valid.

• This reply was modified 6 years, 2 months ago by fluiditystudio.

That doesn’t work. I need to filter out to show only the gray circle under “readability score”. That has the class of “na” on it and in your plugin code (wordpress-seo/admin/formatter/class-metabox-formatter.php) I first shared, it shows..

'na'   => sprintf(
    /* translators: %1$s expands to an opening strong tag, %2$s expands to a closing strong tag. */
    __( 'Readability: %1$sNot available%2$s', 'wordpress-seo' ),
    '<strong>',
    '</strong>'
),

as though this should be an option in the dropdowns with the “bad, ok & good”. However, there is no selection showing for the “Readability: Not available”. Why does it show in your code as an option, but not show up in your plugin?

• This reply was modified 6 years, 7 months ago by fluiditystudio.
• This reply was modified 6 years, 7 months ago by fluiditystudio.

I’m not looking to integrate custom code. I was merely pointing out with the code I posted, that the option for the filter “Readability: Not available” is in your plugin code, but it is not an option available to select in the dropdown from the admin to filter the results. The code posted was exact code from the plugin. I’m trying to find out and understand why the option that appears to be there in the code does not actually show up as an option in the plugin dropdown filter.

I figured it out. Sorry to bother you with it!

I have disabled all plugins accept and under construction plugin (of which wasn’t installed previously), and the google translate plugin and I’m still getting the error. This just recently started happening. I’m wondering if something in the google api changed.

I’m having the same problem, in the console I get the following error when I click on the translate button. “TypeError: this.h[0] is undefined”.

It refers to this file “https://translate.googleapis.com/element/TE_20170911_00/e/js/element/element_main.js”

• This reply was modified 6 years, 11 months ago by fluiditystudio.
• This reply was modified 6 years, 11 months ago by fluiditystudio.
• This reply was modified 6 years, 11 months ago by fluiditystudio.

@ronalfy – I think this plugin is going to end up abandoned, as it hasn’t been updated in 11 months and the author is not responding to anything in the supports threads. My guess is they have given up on this plugin. I have for the time being, changed the code in the plugin to what I stated above. This caused my PHP 7 error to go away.

• This reply was modified 7 years, 2 months ago by fluiditystudio.

You could try my plugin for Software License Manager and WooCommerce. It works great and has more features. It will also allow for renewing license keys at checkout. https://bitbucket.org/fluiditystudio/slm-woocommerce-addon

I have video tutorials on how to use it as well!

• This reply was modified 7 years, 4 months ago by fluiditystudio.

@dennishall – Try my plugin for Software License Manager and WooCommerce. It works great and has more features. It will also allow for renewing license keys at checkout. https://bitbucket.org/fluiditystudio/slm-woocommerce-addon

I even have video tutorials on how to use it!

• This reply was modified 7 years, 4 months ago by fluiditystudio.

The code should be fixed by replacing

ereg(“^[_a-z0-9-]+(\.[_a-z0-9-]+)*@[a-z0-9-]+(\.[a-z0-9-]+)*(\.[a-z]{2,3})$”, $email);

with:

preg_match(‘/^[_a-z0-9-]+(\.[_a-z0-9-]+)*@[a-z0-9-]+(\.[a-z0-9-]+)*(\.[a-z]{2,3})$/’, $email);