Andy Potanin

Thanks for the rating! Actually static assets such as CSS and JS can be uploaded via the Media Library and WP-Stateless will upload them to Google Cloud Storage.

This plugin is meant to synchronize the Media library with Google Cloud Stateless, so as long as the Media Library on your WordPress site allows for for a file type to be uploaded, WP-Stateless will put it on GCS.

Thank you for the positive feedback. Uploading static assets to Google Cloud Storage would be a pretty good idea, are you thinking of just uploading JS and CSS or static HTML pages of the WordPress front-end as well?

If you want to participate in the development of this plugin it would be greatly appreciated. We publish all of our plugins to GitHub where you can fork things, view open issues, and submit fixes. You can see it here: https://github.com/wpCloud/wp-stateless

Thanks for feedback! This is a really good idea that we’ve wanted to implement ourselves as well – in fact this was the original idea for the plugin.

The reason we haven’t added this yet is because some WordPress plugins and themes “get confused” when there is no file on disk (locally), although WordPress itself works just fine. We will add this option soon and will update the idea on feedback.usabilitydynamics.com to keep you, and anybody else who is interested in this, updated.

I believe you already posted this idea on https://feedback.usabilitydynamics.com/forums/353541-wp-statless/suggestions/12927606-add-stateless-mode which is great.

To accommodate existing customers, those using a pre-2.0 version of WP-Property, the purchased licenses will remain available as they are until the end of time. In other words, if you were to keep version 1.42.4 on your site, or install it on a new valid domain, the premium features will be automatically downloaded and available for use as they have in the past. That being said, those legacy features will not be receiving any major updates in the future. So if you want to keep your sites the way they are, don’t upgrade WP-Property to the newer versions.

To keep your site up-to-date with the latest features, you will need to renew your subscription annually. Upgrade renewals are sold at a significant discount which will vary based on how many licenses your account has and for how many years you’ve had a license.

If you’ve already upgraded a site and decide that you’d rather keep using a legacy version of WP-Property along with legacy licenses, you may downgrade by downloading an older version from https://www.ads-software.com/plugins/wp-property/developers/.

Specifically, the error is:

Parse error: syntax error, unexpected $end in /…/wp-content/plugins/network-posts-extended/network-posts-extended.php on line 539

You can also see it in the URL when you’re editing it. Your URL will be something like:

yoursite.com/wp-admin/post.php?post=125&action=edit

125 is the ID.

Hi,

Please create a topic for this on our forum (https://usabilitydynamics.com/forums/) and we’ll check it out for you.

Alaskan,

Your argument about us having a forum offering support, yet not answering your questions, is invalid on many levels. We can start with the most obvious, at the top of the forum there is a large header stating “Community Forums”. The word community strongly implies community interaction, nothing more, nothing less. Furthermore, we set up a page to clear up any further confusion, linked to from nearly every forum page, I am inserting it here in case you missed it: https://usabilitydynamics.com/forum-and-support-policy/

To sum it up, no profit seeking company in the world is going to invest money into labor to answer every single question you may have in the hopes that you may one day spend $20 on a premium feature – that is not cost effective by any measure. Adobe.com, for instance, has no free support, even after you purchase a $999 software.

I am not sure where this entitlement mentality comes from – just because we released a product that we thought others might find useful – does not bind us to eternally helping every single person that may use it. Please familiarize yourself with the GNU license, a part of which I’ll put it here:

“This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.”

We make software, sometimes we release it publicly. We support it to the best of our ability, and have been doing it for a long time. You can browse through thousands of dead plugins and themes on www.ads-software.com if you are curious about the failure rate of free software.

Not really, it’s intended to be a back-end system. If you’re looking for a front-end system, check out Rolo Press (https://rolopress.com/)

You have to click “Show Actions” to do CSV export.

https://usabilitydynamics.com/products/wp-crm/forum/topic/include-existing-usermeta-fields/

Look at the instructions here by the third poster: https://www.ads-software.com/support/topic/probably-hacked-must-change-capabilities-in-phpmyadmin?replies=16

Basically you need to find your profile’s wp_capability entry in the usermeta table, it will most likely be in the meta_key ‘wp_capabilities’

Replace the meta_value with ‘a:1:{s:13:”administrator”;b:1;}’ which is the default capability setting for an administrator.

Or run this query on your DB (be sure to back things up first!) and replace ‘1’ with whatever your user ID is.

UPDATE wp_usermeta SET meta_value = 'a:1:{s:13:"administrator";s:1:"1";}' WHERE meta_key = 'wp_capabilities' AND user_id = '1'

Which submit button? On the contact forms?

bren –

You are right, and sorry about that. Perhaps we jumped the gun on the “public” release, but we didn’t have enough resources to conduct a more thorough QC at the time (we hired a full-time QC tester last week), but had a lot of requests from our customers us to release the plugin into the WP repository, for which I apologize.

To answer your questions.

1. We set up the trash message and user function to make it easy to get rid of spam message and users. Since WP-CRM creates a user account for every person who submits a message, it’s important to be able to delete the user account easily when reviewing messages, in case they are spam, or whatever. We tried to streamline the process as much as possible. However, this has been fixed in the latest release by disallowing deletion of users who were not created via a contact form, and those who have been in the system for over 3 days.

2. We added a confirmation to the deletion to be more professional – via a popup.

3. We didn’t add anything to prevent deletion of site admin since there is no site admin in WordPress, there are various roles, with different capabilities, but there is not a single site admin and defining one (such as user with lowest user ID) would be too subjective.

As far as deletion of all the posts and pages, WP-CRM doesn’t do anything special with that, simply passes arguments to the wp_delete_user() function from the messages screen. When deleting a user from the profile screen, there are additional checks, and a function that copies all the attached objects to the user performing the deletion action, to prevent them from being lost.

That’s what I figured. We’ll have to put something into the code to prevent the plugin from running on older versions of WP so this doesn’t happen to others.

Also, in the future please consider using our forums for questions: https://usabilitydynamics.com/forums/

rweakly – what version of WP are you using?