rbschneider1

I marked this “Resolved” the other day when I thought it was resolved. Can you change it back to unresolved?

Would like to know if there is a fix for this, or if I can manually change the db field that holds the Sequential Starting Number?

I just did a fresh install of WordPress (4.2.2) using Twenty Thirteen theme with no other plugins except EDD. Having the same issue as stated above.

I did one test not using a Sequential Order Number, the order number started at 11 (I believe).

I then enabled Sequential Order Number and set the Sequential Starting Number to 2100 and did the update. It updated past numbers in the Payment History, and on a new purchase, it did show the correct number 2101.

I then changed the Sequential Starting Number to 3100, did the the “Update”. It updated past numbers in the Payment History, but on a new purchase, it was still showing (2100), not the (3100) start number.

Still having problems with the Sequential Start Number.

I did the “Update” and was able to see the Sequential Order Number changed on all prior orders for customers, but when I do a new purchase, it’s still not updating the new starting number, still getting ARE-10-OC when it should be ARE-1403-OC. Seems the number in the db is not being updated with the new Sequential Start Number.

I just found the link to the “update” database on top.

Sorry about that, I didn’t think of looking there for it.

Thanks for the reply…….

No, how do I do this?
I just changed the starting number “2100”, then saved it.

Additional Info:

Here’s the info from the database:
_options
edd_settings:
s:16:”sequential_start”;s:4:”2100″;s:17:”sequential_prefix”;s:3:”ARE”;s:18:”sequential_postfix”;s:2:”OC”;

Thanks for the reply..

UPDATE:

Never mind Sunny, I checkout the extension “Checkout Fields Manager” and decided to purchase it. Looks like it’s exactly what I need.

Thanks for everything…….

Sunny,

Would you be willing to sharing how I would do this – “1. You’d need to do an advanced MySQL query to retrieve this data. I’m assuming you’re familiar with MySQL? You’d need to use the JOIN functions to join up the posts and post meta tables in WordPress as well as DATE query functions to get all the meta values from the previous month.”?

I really like this plugin & support, everything was working great, until I ran into this issue. It’s a must have for my application.

Thanks in advance…….

Sunny,

Thanks for your quick reply.

I know a little about MySQL, but I think your talking above my head. Not sure how to set the query up for for this.

Thanks again for your help.

It would help if you explain your reply “adding the field to the profile form twice that way”.

Never mind, I’ll look elsewhere for answers.

Add to register-form.php (child-theme dir)

<p>
<label for="asq_id<?php $template->the_instance(); ?>"><?php _e( 'ASQ Section#', 'theme-my-login' ) ?></label>
<input type="number" name="asq_id" id="asq_id<?php $template->the_instance(); ?>" class="input" value="<?php $template->the_posted_value( 'asq_id' ); ?>" size="4" />
</p>

Add to profile-form.php (child-theme dir)

<h3><?php _e( 'Enter Your ASQ Section ID#', 'theme-my-login' ); ?></h3>
<table class="form-table">
<tr>
<th><label for="asq_id"><?php _e( 'ASQ Section ID#:', 'theme-my-login' ); ?></label></th>
<td><input type="number" name="asq_id" id="asq_id" min="0001" max="9999" value="<?php echo esc_attr( $profileuser->asq_id ); ?>" /></td>
</tr>
</table>

Add to theme-my-login-custom.php (plugins root dir)

function tml_edit_user_profile( $profileuser ) {
?>
<p>
<label for="asq_id">ASQ Section#</label>
<input type="number" name="asq_id" id="asq_id" min="0001" max="9999" value="<?php echo esc_attr( $profileuser->asq_id ); ?>" />
</p>
<?php
}
add_action( 'edit_user_profile', 'tml_edit_user_profile' );
function tml_user_register( $user_id ) {
if ( !empty( $_POST['asq_id'] ) )
	update_user_meta( $user_id, 'asq_id', $_POST['asq_id'] );
}
add_action( 'user_register', 'tml_user_register' );

Sorry Jeff, just relized I should have used the “code button” to post the coding.

Yep, your right.

It ended up being css conflicts with my theme (Twenty-Thirteen). Was able to correct with css.

Thanks for your reply Jeff……

I belief I just found the problem.

I deactivated my custom css plug-in (Simple Custom CSS) and it now displays correctly. I’m guessing something needs to be corrected in the custom css I added.

Is it possible that there is a conflict with this plug-in (Simple Custom CSS)? Just a thought.

I will update this post with what was the actual cause (I’m sure it was me..lol).