Hi Benji, I see that there's some confusion now and the Nastia's macro misses a cf at the start so let me go over this in detail one more time. So the meta_key value is pulled from Field Name: [attachment=1406185,131549] So in SC you should use %%cf_my_custom_field%% like this: [attachment=1406185,131550] And now what you enter as ACF value should be used as title: [attachment=1406185,131551] [attachment=1406185,131552] Hope this clears things up now :) Best regards, Predrag

Hi Leo, We would need support access to assist you further because some changes need to be done from plugin settings and not CSS. To enable support access you can follow this guide here: https://premium.wpmudev.org/docs/getting-started/getting-support/#chapter-5 Please respond in this ticket once access is granted. Best regards, Predrag

Hi stripedrhino, Can you try following these steps and let us know if that is the information that you can use: - Have one member with a membership - Navigate to Membership 2 > All Members page - Click on the Profile icon on the far right side for one of your members - In the Payments column inside popup click on Payment amount - Now nex to Invoice ID click on Show Transaction - Once there, in the Details column hover on the Info icon and that should expand you payment details and I believe that those are the values that can be used in iDevAffiliate [attachment=1406169,131548] Best regards, Predrag

Hi Michael, Apologies for the delay here, we work on tickets from oldest response to newest and your responses pushed it further down the queue each time. I had a closer look at your installation now and I'm afraid that it's completely unclear what is causing this and based on your current site look I would suggest creating a staging site and doing some cleanup there in order to try and determine the issue. First thing that you should do, and the easiest step, is to check for any conflicts. You can do that by disabling all of your plugins except for BuddyPress and switch to default WP theme to see if it works after that. If that doesn't help then some further cleanup, like I mentioned above might be needed. I'm saying this because in addition to a lot of rules in your .htaccess file there are also some additional defines in your wp-config.php. In addition to that you also have addtional .htaccess files in other folders and some leftover folders from old plugins like W3TC and some other non-WP folders, especially inside wp-content folder. So my suggestion here, if the conflict test doesn't work, is to clear up all of that non-standard defines and files/folders that you have on your site and then give it another test after that. Since this can affect your installation I strongly suggest doing these tests on a staging site as I mentioned at the start of my message. Best regards, Predrag

Hi Wendy, I understand your frustration, Shipper is still a young plugin and even though we have tested it on over a dozen different servers it was impossible to test on all of the combinations available out there but hopefully once the devs figure out the issue here it will help us to further improve the plugin for any future cases like these. Best regards, Predrag

Hi Mark, Would you mind allowing support access so we can have a closer look at all of the settings and try doing some tests on our end with a similar form? To enable support access you can follow this guide here: https://premium.wpmudev.org/docs/getting-started/getting-support/#chapter-5 Please respond in this ticket once access is granted. Best regards, Predrag

Hi John, I'm not completely sure as you have almost 50 plugins active and I'm not familiar with most of them. Could you perform a quick conflict test on live site so we can see if this is indeed caused by any of them? You can go to Hosting panel and in Tools tab enable password protection so that the users are not greeted with a broken site. Go to Backups tab and create a backup of your site. After that disable all of the plugins except for e-Newsletter and send out a new newsletter via cron to see if it works. If it works that means that we're indeed dealing with a conflict test and you can activate the plugins one by one until you find a culprit. Once the test is done you can easily restore to your backup to get the site to the exact same state as before the test and disable password protection. Best regards, Predrag

Hi Lee, I changed the ZIP method so that the process is slowed down but to make less hit on the server resources and I was able to create a Snapshot of your main site without any problems. Can you check it as well and see if it works fine now? Best regards, Predrag

Hi Benji, This would be possible to do by using a variable like this: %%cf_acf_meta_key%% Where acf_meta_key is meta_key value of your ACF field from wp_postmeta table. Hope this helps. Best regards, Predrag

Hi ferreirex, I saw this when I visited your Themes panel in Marias subsite. I wanted to grab you a screenshot but I see that you have already updated the theme, but basically on top of Themes page there was a notification about an available update for Alpenhouse theme. Best regards, Predrag