midnitedev

Hi Marko, yes but instead of the 200, I’m receiving the 500 error on production and just shows the loading icon indefinitely. But on local, it successfully shows the correct stats. Are there any particular files that I should look into that causes it?

There are no other references to the error on the server side except for this: httpd access log shows /wp-admin/admin-ajax.php?action=w3tc_ajax&_wpnonce=xxxxxxxxx&w3tc_action=pagespeed_widgetdata&_fs_blog_admin=true HTTP/1.1″ 504

Thanks for showing the way. Appreciate it.

Hi @catacaustic, data communication will be 2-way, plugin users will be able to see messages from our platform and we should see theirs on ours when they send them. I’m thinking that an api key would serve the purpose here as the connector should the api be ready for production. One of the purposes that data would most likely be for is real-time messaging, but also for scheduling, message history, etc.

@vmarko

The solution has worked! I’m now able to upload theme files, custom, etc. to CDN. Thanks.

Hi Marko,

None that I know of. However, I’m using this on my functions.php file since I installed aws-sdk via composer (and using the following lines below based on documentation aws):

require ABSPATH.'vendor/autoload.php';
use Aws\S3\S3Client;
use Aws\Exception\AwsException;

Previously, we had these lines of code, which was replaced by the one above because it was causing a server 500 error when it was uncommented.

//import aws sdk
//     require_once ABSPATH."aws-sdk/aws-autoloader.php";

where aws-sdk was an unzipped version of aws-sdk until using the Composer-installed version.

I resolved it by upgrading W3TC plugin to v0.15.1. I think this was related to W3TC’s previous version (0.15.0) handling of memcache or some other issue since they mentioned in the update notes and the upgrade solved the redirect problem.

Hi Andrew, yes I am on version 2.3.3. I checked the login page and it is indeed the case. Thank you!

@andrewza I tested it, so it has a weird behavior in that on $email -> subject, where I use !!sitename!! it fails on the email received. It shows !!sitename!! on the subject line (gmail)

On $email -> body however, !!validation_link!! works. I get an actual link on the subject body of the email confirmation I receive.

I guess I also have to disable the add-on to enable the changes on pmpro-customizations.php for the email confirmation template.

@andrewza Thank you very much, I’ll try it out. I do have a couple of questions though,

a) does this overwrite the email template add-on custom changes? if not, then do I need to just remove the changes made there or do I need to deactivate/remove the add-on?

b) when calling some variables, for example, validation link which in the add-on is referred to as !!validation_link!!, do we have an equivalent for calling it in that code? I’ve been looking for some thing similar such as $user -> validation_link or anything similar.

c) this might not be particularly related considering its a customization issue, but I haven’t seen this custom code on the pmpro website so I assume the plugin or any add-ons doesn’t include this. Is this custom code going to be a part in future versions of plugin/add-on or is this solely for specific user requirements and at the moment just used for reference?

Thanks.

I’ve fixed the issue. Thank you for your help.

So I’m currently focusing on the custom checkout.php page where the customizations are made. As far as the customizations, the ones added are css styles, js code to toggle a specific section of code on a checkbox status:

jQuery(document).ready(function(){

		jQuery('#add_admin_contact').on('click',function (e){
		    jQuery('#pmpro_administrative_fields').toggle();
		});
	})

the html/php code to show related to the code above:

<div id="pmpro_administrative_fields" class="pmpro_checkout" style="display:none;">
				<h3>
					<span class="pmpro_checkout-h3-name"><?php _e('Trusted Personal Contact', 'paid-memberships-pro' );?></span>
				</h3>
			</div> 

and the header code:

<div id="signUpHeader" class="lazy-load-bg">
		<img data-src="/images/signup-img.png">

			<p style="display: none;">
				<?php printf(__('You have selected the <strong>%s</strong> membership level.', 'paid-memberships-pro' ), $pmpro_level->name);?>
			</p>
			<?php
				/**
				 * All devs to filter the level description at checkout.
				 * We also have a function in includes/filters.php that applies the the_content filters to this description.
				 * @param string $description The level description.
				 * @param object $pmpro_level The PMPro Level object.
				 */
				$level_description = apply_filters('pmpro_level_description', $pmpro_level->description, $pmpro_level);
				if(!empty($level_description))
					echo $level_description;
			?>

	</div>

I’m fairly sure these code parts are not causing the issue. I keep going back to this code:

//make sure javascript is ok
	if ( apply_filters( "pmpro_require_javascript_for_checkout", true ) && ! empty( $_REQUEST['checkjavascript'] ) && empty( $_REQUEST['javascriptok'] ) ) {
		pmpro_setMessage( __( "There are JavaScript errors on the page. Please contact the webmaster.", 'paid-memberships-pro' ), "pmpro_error" );
	}

since this is what I find to be executing (it works on free trial and paid signups but fails on free trial to paid transition). javascriptok and checkjavascript variables are both 1 on all levels (regular signup, free trial and free trial to paid) so it can’t be on these variables. That leaves pmpro_require_javascript_for_checkout.

Btw, I couldn’t find anything much on pmpro_require_javascript_for_checkout. The only reference to it is from /plugins/paid-memberships-pro/preheaders/checkout.php

Thanks, now I’m getting somewhere. So previously I already tried disabling plugins (plugin User Menus left because it breaks the site, PMPro left as well including its add-ons), I redid the same thing today and tested it prior and still got the same error. I switched to the Twenty Twenty theme and now the free trial to paid membership successfully processed.

Hi Andrew,

I have been able to recreate this issue again, but I’m not getting any javascript errors. The only console notes and warnings I get are the ff when pressing submit:

JQMIGRATE: Migrate is installed, version 1.4.1
DevTools failed to parse SourceMap: https://duoypevs5mcpk.cloudfront.net/wp-content/themes/livinglegacy/includes/js/bootstrap.min.js.map
DevTools failed to parse SourceMap: https://duoypevs5mcpk.cloudfront.net/wp-content/themes/livinglegacy/includes/css/bootstrap.min.css.map

That is it. The condition is triggered by this specific snippet in …/paid-memberships-pro/preheaders/checkout.php:

//make sure javascript is ok
	if ( apply_filters( "pmpro_require_javascript_for_checkout", true ) && ! empty( $_REQUEST['checkjavascript'] ) && empty( $_REQUEST['javascriptok'] ) ) {
		pmpro_setMessage( __( "There are JavaScript errors on the page. Please contact the webmaster.", 'paid-memberships-pro' ), "pmpro_error" );
	}

@t-p I found out how to fix it. .DS_Store for some reason on OS X High Sierra and up requires turning off System Integrity Protection to properly see. I ran across this post to help me zip up a theme but ignore the .DS_Store files to properly upload it to www.ads-software.com (https://ahmadawais.com/zip-wordpress-theme-through-terminal-and-ignore-ds_store/).

Helped me submit my theme without major hitches. Thanks for your help as well.

• This reply was modified 5 years, 2 months ago by midnitedev.

@t-p Thanks, I looked at the sources but I have no idea how this could help me on my current issue. I honestly don’t see the issue of deleting them, I’ve deleted them before on previous projects. It’s also on an OS X device. The issue is that theme upload for the WordPress theme directory (https://www.ads-software.com/themes/upload/) is not accepting my theme due to this issue of a .ds_store file that I can’t see even though I ran commands to find and delete it (its non-existent basically).

Here are the errors I’m getting when uploading my theme:

Results of Automated Theme Scanning: Fail
WARNING: .ds_store Hidden Files or Folders found.
INFO: Only one text-domain is being used in this theme. Make sure it matches the theme’s slug correctly so that the theme will be compatible with www.ads-software.com language packs.