davidwtalley

Thanks Jackie. The WordPress install is in the /wordpress subdirectory. Top-level URL is:

https://explore.dublincore.net/

**** .htaccess: ***

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]

#RedirectMatch 301 ^/wordpress/$ [snip]

</IfModule>

# END WordPress

*** wp-config.php: ***

<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, and ABSPATH. You can find more information by visiting
* {@link https://codex.www.ads-software.com/Editing_wp-config.php Editing wp-config.php}
* Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don’t have to use the web site, you can just copy this file
* to “wp-config.php” and fill in the values.
*
* @package WordPress
*/

// ** MySQL settings – You can get this info from your web host ** //
/** The name of the database for WordPress */
define(‘DB_NAME’, ‘[snip]’);

/** MySQL database username */
define(‘DB_USER’, ‘[snip]’);

/** MySQL database password */
define(‘DB_PASSWORD’, ‘[snip]’);

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);

/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8’);

/** The Database Collate type. Don’t change this if in doubt. */
define(‘DB_COLLATE’, ”);

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define(‘AUTH_KEY’, ‘[snip]’);
define(‘SECURE_AUTH_KEY’, ‘[snip]’);
define(‘LOGGED_IN_KEY’, ‘[snip]’);
define(‘NONCE_KEY’, ‘[snip]’);
define(‘AUTH_SALT’, ‘[snip]’);
define(‘SECURE_AUTH_SALT’, ‘[snip]’);
define(‘LOGGED_IN_SALT’, ‘[snip]’);
define(‘NONCE_SALT’, ‘[snip]’);

/**#@-*/

/**
* WordPress Database Table prefix.
*
* You can have multiple installations in one database if you give each a unique
* prefix. Only numbers, letters, and underscores please!
*/
$table_prefix = ‘wp_’;

/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*/
define(‘WP_DEBUG’, false);

/* That’s all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

/* Multisite */
define( ‘WP_ALLOW_MULTISITE’, true );
define(‘MULTISITE’, true);
define(‘SUBDOMAIN_INSTALL’, true);
define(‘DOMAIN_CURRENT_SITE’, ‘[snip]’);
define(‘PATH_CURRENT_SITE’, ‘/’);
define(‘SITE_ID_CURRENT_SITE’, 1);
define(‘BLOG_ID_CURRENT_SITE’, 1);

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . ‘wp-settings.php’);

No, my need is much simpler: For any listing of posts, display items sorted by rating. Would the Sort WP Loop function here do that?

https://danielpowney.com/docs/code-snippets-api-samples/

I haven’t been able to get it to work so far.

Hey, elisite.

I had the same issue. I had thoughts of using the first function, Sort WP Loop, on this page. Daniel, does that sound like the right approach?

https://danielpowney.com/docs/code-snippets-api-samples/

Also, I would like to validate that I can get that to work before buying the Pro version (which looks like a very solid investment, btw!). Would I need to make changes to that function to work with the public version?

I do have admin rights for the WordPress instance. If I did not have admin rights, I could not see the Settings page to check the checkbox and generate the error, right? Or are you referring to admin rights for the plug-in specifically? If so, how do those rights get set?

Does the plug-in install require any change to the file /wp-admin/options.php?