miketopher

Thanks for the reply.

I may have asked incorrectly, so… Does your plugin support the different payment gateway plugins?

I’m using https://www.ads-software.com/plugins/woo-stripe-payment/ which supports ach through stripe.

I would like to know if I could use your subscription plugin, combined with https://www.ads-software.com/plugins/woo-stripe-payment/ ach method so i can regularly auto-charge a customer through ach.

Thanks!

Did you really need to call me out though? trying to build a reputation here on the forum.. thanks bud

I think you’re right, try this:

if($modo_vista_proyecto == "cuadricula") { ?>
  <h2><?php echo get_the_title($loop); ?></h2>
  <?php echo the_content(); 
}
if ($modo_vista_proyecto == "tabla") { ?>
  <h2><?php echo get_the_title($loop); ?> oook</h2> 
<?php }

Because it’s a real solution, don’t use blocks. You even said you don’t care for them, I thought I would suggest that you disable that system, might be easier to customize and do what you want, the ol’ fashion way.

And what kind of weirdo doesn’t like eggs?

You’re very welcome!

Hosting providers that offer WP-CLI access to all users typically do so by running WP-CLI in a restricted environment where users do not have access to the underlying system. This could be done using a containerization technology such as Docker or by using a serverless architecture where each user is given a dedicated environment for running WP-CLI commands.

The “dedicated environment” is not a physically dedicated machine, but the software is configured in a way, where it is essentially, physically dedicated, or at least “your dedicated environment believes it is physically separate” more or less…

I didn’t notice that before, but I found this one https://www.ads-software.com/plugins/simply-static/

And this video https://www.youtube.com/watch?v=kO-PCcpvaDI that might help walk through it.

Assuming you want to do this on the single posts, and not archives, etc…

Try this code in your code snippets plugin:

function get_last_modified_date() {
  if ( is_single() ) { // only display the last modified date on single posts
    $post_id = get_the_ID(); // get the current post ID
    $last_modified_date = get_post_modified_time('F j, Y', false, $post_id, false); // get the last modified date in the desired format
    return $last_modified_date; // return the last modified date
  }
}

There are a few different ways you can save a static WordPress website as raw HTML and CSS to your computer so you can view the website without an internet connection. Here are a few options:

Use a tool like HTTrack or WinHTTrack to download the entire website and save it to your computer. These tools allow you to specify the URL of the website you want to download, and they will automatically download all of the HTML, CSS, and other assets required to view the website offline.

Use the “Save As” feature in your web browser to save the website as a single HTML file. This will save the current state of the website as a single HTML file, but it will not include any of the associated CSS or other assets required to properly render the website.

Use a plugin like “WP Static HTML Output” to generate static HTML files for your WordPress website. This plugin allows you to export your entire WordPress website as a set of static HTML files, which you can then download and view offline on your computer.

You could also consider hosting free on wordpress.com hosted website. If you cant pay a bill later, you would not be able to have a custom domain, but you could just use the free sub domain that wordpress.com gives you.

Though make sure to read their terms, not sure if they delete inactive websites or not after some time.

You should first use a theme, or builder such as Oxygen that is built specifically for max performance, by not loading unnecessary things.

Then use plugins like https://www.ads-software.com/plugins/freesoul-deactivate-plugins/ to remove plugins ability to “run” on the server, when accessing front-end pages, almost every wordpress website is doing this and it slows down a lot of things. This plugin also prevents entire plugins from loading on the front end, on pages which they are not required.

You will need to spend some time working with this out, no one can really tell you a simple way to do this, you have to simply understand more deeply how things work, and then build your website properly.

One option you could consider is creating a wrapper script for WP-CLI that allows non-root users to use it. To do this, you can create a script called wp in a directory that is in the PATH for all users, such as /usr/local/bin. The script would contain the following content:

#!/bin/bash

sudo -u root /path/to/wp-cli "$@"

This script will run WP-CLI as the root user when it is invoked by a non-root user. You will need to make sure that the /path/to/wp-cli is correct and that the script is executable by all users (you can do this by running chmod 755 /usr/local/bin/wp).

Once you have created the wrapper script, users should be able to run WP-CLI commands by simply typing wp followed by the desired command and arguments. For example:

wp plugin list

This will run the plugin list command as the root user, allowing non-root users to use WP-CLI.

Keep in mind that this approach will allow any user on the system to run WP-CLI as the root user, so you should use caution when setting this up and consider the potential security implications.

Sorry to not really answer your question but if you’re in that camp, then don’t use blocks. Use the disable gutenberg plugin and build the site normally.

Sorry I don’t know the answer otherwise, cause i dont touch blocks.

fyi

In WordPress, the nopriv parameter of the add_action function specifies that the action should be executed for users who are not logged in. So, if you add an additional add_action call without the nopriv parameter, it will be executed for both logged-in and logged-out users.

It’s worth noting that the nopriv parameter is usually used in conjunction with the wp_ajax_nopriv_ prefix, which specifies that the action should be triggered when an Ajax request is made by a logged-out user. The wp_ajax_ prefix, on the other hand, specifies that the action should be triggered when an Ajax request is made by a logged-in user.

To replace the use of get_the_title() with the conditional that you provided, you can try the following approach:

1. Replace get_the_title() with get_the_title(get_the_ID()). This will allow you to pass the post ID as an argument to get_the_title() so that you can get the title of the current post in the loop.
2. Replace var_dump($loop) with the following block of code:

if($modo_vista_proyecto == "cuadricula") { ?>
  <h2><?php echo get_the_title(get_the_ID()); ?></h2>
  <?php echo the_content(); 
}
if ($modo_vista_proyecto == "tabla") { ?>
  <h2><?php echo get_the_title(get_the_ID()); ?> oook</h2> 
<?php }

This should output the title and content of the current post in the loop, depending on the value of $modo_vista_proyecto.

It’s also worth noting that the var_dump() function is used for debugging purposes and is not typically used in production code. Instead of using var_dump(), you may want to consider using a more appropriate function to output the data, such as echo or print_r().

There could be a few reasons why the WP_User_Query is ignoring the meta_query when run from an AJAX function. Here are a few things you can try to troubleshoot the issue:

1. Make sure that you are correctly enqueuing the script that contains the AJAX function and that the script is correctly registered and localized.
2. Check the $_POST data that is being passed to the AJAX function to make sure that it contains the correct meta_query arguments.
3. Make sure that the meta_query arguments are being correctly passed to the WP_User_Query constructor. You can try printing out the $args2 array before the WP_User_Query is run to verify that the meta_query is present.
4. Check the WordPress debug log for any errors or warnings that may be related to the WP_User_Query or the AJAX function.
5. Make sure that the usermeta table and the gender meta key exist in the database and that they have the correct permissions.

Hope this helps.

eh, sorry I was completely forgetting the wp_postmeta table that had multiple instances of the guid as well that were actually responsible for the display of the “file url” in the media attachment page. So i just ran that and it worked