Title: Plugin is not working
Last modified: July 18, 2022

---

# Plugin is not working

 *  [Hari](https://wordpress.org/support/users/haribonda/)
 * (@haribonda)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/plugin-is-not-working-167/)
 * hi, I have the latest WordPress and woo commerce versions installed when I activate
   the plugin and visit the plugin page it is not working and shows an error, does
   it working directory installations?
 * and also google Cloud Messaging is REMOVED 5/29/2018 [https://developers.google.com/cloud-messaging](https://developers.google.com/cloud-messaging)
 * could you help me get this running
 * another question: Instead of relying on Google services can we just use IFTTT?
 * ——————————-
 * There has been a critical error on this website. Please check your site admin
   email inbox for instructions.
 *     ```
       Howdy!
   
       Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
   
       In this case, WordPress caught an error with one of your plugins, Free SMS for WooCommerce.
   
       First, visit your website (https://www.domain.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.domain.com/wp-admin/admin.php?page=free-sms) and check for any visible issues.
   
       Please contact your host for assistance with investigating this issue further.
   
       If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.
   
       https://www.domain.com/wp-login.php?action=enter_recovery_mode&rm_token=W2jMA0102mhP8s6ticDOuIBq7&rm_key=Tce7im8k89LmxkMkqfBfJg
   
       To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.
   
       When seeking help with this issue, you may be asked for some of the following information:
       WordPress version 6.0.1
       Active theme: Twenty Twenty-One (version 1.4)
       Current plugin: Free SMS for WooCommerce (version 1.0.0)
       PHP version 7.4.30
   
       Error Details
       =============
       An error of type E_PARSE was caused in line 193 of the file /home/0.cloudwaysapps.com/0/public_html/domain/wp-content/plugins/free-sms-for-woocommerce/page.php. Error message: syntax error, unexpected 'endif' (T_ENDIF)
       ```
   
    -  This topic was modified 3 years, 11 months ago by [Hari](https://wordpress.org/support/users/haribonda/).

Viewing 1 replies (of 1 total)

 *  Plugin Author [bjuriewicz](https://wordpress.org/support/users/bjuriewicz/)
 * (@bjuriewicz)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/plugin-is-not-working-167/#post-15853863)
 * Hello Hari,
    the plugin server uses FCM (firebase cloud message), not GCM – I
   must have used the GCM name by accident. Regarding the error message – could 
   you please make sure the `short_open_tag` option in your php.ini is enabled?

Viewing 1 replies (of 1 total)

The topic ‘Plugin is not working’ is closed to new replies.

 * ![](https://ps.w.org/free-sms-for-woocommerce/assets/icon-256x256.png?rev=2416706)
 * [Free SMS for WooCommerce](https://wordpress.org/plugins/free-sms-for-woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/free-sms-for-woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/free-sms-for-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/free-sms-for-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/free-sms-for-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/free-sms-for-woocommerce/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [bjuriewicz](https://wordpress.org/support/users/bjuriewicz/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/plugin-is-not-working-167/#post-15853863)
 * Status: not resolved