Aakash

Hi @martinxun03

reCAPTCHA is also supported, see the official WPForms guide for that here.

Various multi-column layout possibilities are also available. WHat you described is possible. Here is a guide on how to utilize multi-column layouts.

Hope this helped, enjoy the plugin!

I believe this is typically due to a plugin conflict.

If you can check which plugin is causing the conflict and let both WPForms and the other plugin’s developers know, it should get patched.

During my research I noticed this similar post. If you’re using that plugin, try following what’s suggested in that thread/updating the plugin.

Being on PHP 7.4 or higher or reinstalling the plugin may also help in some cases.

Good luck

Hi @alyssumtr

Yes this is possible. Here’s the guide on How to Redirect Users to a New Page .

Hope this helped!

Hi @jespersw

Looks like you’re not alone experiencing this reCAPTCHA issue, there’s quite a long thread about it on their GitHub page here.

The good news is, there was a solution in the comments! You can add this CSS code to make it responsive.

@media screen and (max-height: 575px){
     #rc-imageselect, .g-recaptcha {
         transform:scale(0.77);
         -webkit-transform:scale(0.77);
         transform-origin:0 0;
         -webkit-transform-origin:0 0;
    }
}

Hope this helped!

Hi @baytocruz

If you could provide a link that demonstrates the form, I can share CSS code to help accomplish this.

HI @letsscrap

Try following the steps outlined in this guide if you haven’t already – https://wpforms.com/docs/how-to-troubleshoot-action-scheduler-issues-in-wpforms/

Also try this:
– Disable All Plugins
– Switch to the default WordPress theme
– Delete and install the latest version of: WPForms, WooCommerce, and Action Scheduler
– Make sure you’re on the latest version of WordPress and ideally PHP 7.4 or greater
– If issue persists, can also try installing WooCommerce via FTP

Hope this helped, good luck!

Hi @martinpwph

The @ in {residential[1]/objects[1]/img[8]/@modTime} is indicating which attribute value to grab, in this case, modTime.

If you change this to {residential[1]/objects[1]/img[8]/@url} it will target https://agentboxcdn.com.au/clients-data/22298/public_html/media/lt/54/54P2120/165992495051391575-rsd.jpg

Hope this helped clear things up.

Hi @drseo

Here’s some basic PHP code to both download and upload files via FTP.

function ftp_download() {
  $ftphost = "ftp.yourwebsite.com";
  $ftpuser = "[email protected]";
  $ftppass = "password";
  $source = "/some_folder/public_html/wp-content/uploads/target_file.xml"; // Source file on server
  $destination = "downloaded.xml"; // Save to this file

  $ftp = ftp_connect($ftphost) or die("Failed to connect to $ftphost");
  
  if (ftp_login($ftp, $ftpuser, $ftppass)) {
    echo ftp_get($ftp, $destination, $source, FTP_BINARY)
      ? "Saved to $destination"
      : "Error downloading $source" ;
  } else { echo "Invalid user/password"; }
  
  ftp_close($ftp);
}

function ftp_upload() {
  $ftphost = "ftp.yourwebsite.com";
  $ftpuser = "[email protected]";
  $ftppass = "password";
  $source = "/some_folder/on_my_pc/downloaded.xml"; // Source file on server
  $destination = "/wp-content/uploads/wpallimport/files/downloaded.xml"; // Save to this file on FTP server
  
  $ftp = ftp_connect($ftphost) or die("Failed to connect to $ftphost");
  
  if (ftp_login($ftp, $ftpuser, $ftppass)) {
    echo ftp_put($ftp, $destination, $source, FTP_BINARY)
      ? "Uploaded to $destination"
      : "Error uploading $source" ;
  } else { echo "Invalid user/password"; }
  
  ftp_close($ftp);
}

If someone could explain what the next steps are, I could attempt to whip up some additional code for that.

Hope this helped get you closer to your goal!

Hi @justte1

Yes, all of this should be possible.

If you could share a example XML file and screenshots of your import settings, users can take a look and assist further.

This relevant section of the documentation along with some videos may help further:https://www.wpallimport.com/documentation/theme-plugin-fields/

@zookie_333

It’s possible that your import file may be malformatted. Maybe a line past line 1,000 contains the issue.

Try importing it in larger and larger chunks to help pinpoint the possible issue.
Or try running it through a XML (or appropriate) validator like this.

If you could share the file here, maybe someone else could take it look.

Hi @ksgboy22

Utilizing WP All Import’s custom PHP function feature would be one way to accomplish this.

Place the code below into the Function Editor mentioned above.
Replace [su_highlight] and [\su_highlight] with your desired shortcode’s requirements.

<?php
function enclose_in_shortcode( $text = null) {
return "[su_highlight]" . $text . "[/su_highlight]"; 
}

Then, in the field where you’d like to place the shortcode, put this:
[enclose_in_shortcode({miasta[1]})]

Hope this helped out!

Hi @18tommyboy

You should be able to extract the URL via PHP by placing this value in the field where you’d like it:
[strtok({your_URL[1]}, '?')]

Here’s more info on how to use inline PHP in WP ALl Import.

Hope this helped.

@stanleymog Good news, got it figured out!

How to remove deleted WooCommerce items via WP All Import

• In the WordPress admin sidebar, navigate to All Import > Manage Imports
• Hover over the desired import, and click Settings
• Upload your new import file
• In the Record Matching section, check the box for Delete products that are no longer present in your file*
• Click Save Import Configuration
• Click Run Import

*There are additional options to perform other actions on deleted products which can be seen here:

Screen Shot 2022-09-02 at 11.29.28 PM

Hope this helped!

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

Hi @stanleymog

This post from the dev is a bit old, but may help.
https://www.ads-software.com/support/topic/delete-products-from-webshop-that-are-no-longer-present-in-the-file/#post-13289863

Can you share any specific error logs/debug messages related to this? Will help track down the issue.

Sicne it seems to be related to a theme update, perhaps contact the theme developers as well to check for a conflict.