isaaa

FIXED – cause: corrupt certificates

I removed a DRAFT certificate and 7 corrupt certificates.
I Updated Data for certificates

The 7 corrupt certificates appeared in table without any Learner or Course displayed. All 8 were for same learner and course.

After making this change, my page with the shortcode returned empty.
I put shortcode on a new page and previewed.
Results
=======
array(1) {
[339]=>
object(WC_Order_Item_Product)#5291 (11) {
[“extra_data”:protected]=>
array(9) {
[“product_id”]=>
int(0)
[“variation_id”]=>
int(0)
[“quantity”]=>
int(1)
[“tax_class”]=>
string(0) “”
[“subtotal”]=>
int(0)
[“subtotal_tax”]=>
int(0)
[“total”]=>
int(0)
[“total_tax”]=>
int(0)
[“taxes”]=>
array(2) {
[“subtotal”]=>
array(0) {
}
[“total”]=>
array(0) {
}
}
}
[“data”:protected]=>
array(11) {
[“order_id”]=>
int(8664)
[“name”]=>
string(11) “Dorme WA-03”
[“product_id”]=>
int(7541)
[“variation_id”]=>
int(0)
[“quantity”]=>
int(1)
[“tax_class”]=>
string(0) “”
[“subtotal”]=>
string(2) “41”
[“subtotal_tax”]=>
string(1) “0”
[“total”]=>
string(1) “0”
[“total_tax”]=>
string(1) “0”
[“taxes”]=>
array(2) {
[“total”]=>
array(0) {
}
[“subtotal”]=>
array(0) {
}
}
}
[“cache_group”:protected]=>
string(11) “order-items”
[“meta_type”:protected]=>
string(10) “order_item”
[“object_type”:protected]=>
string(10) “order_item”
[“id”:protected]=>
int(339)
[“changes”:protected]=>
array(0) {
}
[“object_read”:protected]=>
bool(true)
[“default_data”:protected]=>
array(11) {
[“order_id”]=>
int(0)
[“name”]=>
string(0) “”
[“product_id”]=>
int(0)
[“variation_id”]=>
int(0)
[“quantity”]=>
int(1)
[“tax_class”]=>
string(0) “”
[“subtotal”]=>
int(0)
[“subtotal_tax”]=>
int(0)
[“total”]=>
int(0)
[“total_tax”]=>
int(0)
[“taxes”]=>
array(2) {
[“subtotal”]=>
array(0) {
}
[“total”]=>
array(0) {
}
}
}
[“data_store”:protected]=>
object(WC_Data_Store)#5248 (4) {
[“instance”:”WC_Data_Store”:private]=>
object(WC_Order_Item_Product_Data_Store)#5812 (4) {
[“internal_meta_keys”:protected]=>
array(20) {
[0]=>
string(9) “_order_id”
[1]=>
string(5) “_name”
[2]=>
string(11) “_product_id”
[3]=>
string(13) “_variation_id”
[4]=>
string(9) “_quantity”
[5]=>
string(10) “_tax_class”
[6]=>
string(9) “_subtotal”
[7]=>
string(13) “_subtotal_tax”
[8]=>
string(6) “_total”
[9]=>
string(10) “_total_tax”
[10]=>
string(6) “_taxes”
[11]=>
string(11) “_product_id”
[12]=>
string(13) “_variation_id”
[13]=>
string(4) “_qty”
[14]=>
string(10) “_tax_class”
[15]=>
string(14) “_line_subtotal”
[16]=>
string(18) “_line_subtotal_tax”
[17]=>
string(11) “_line_total”
[18]=>
string(9) “_line_tax”
[19]=>
string(14) “_line_tax_data”
}
[“meta_type”:protected]=>
string(10) “order_item”
[“object_id_field_for_meta”:protected]=>
string(13) “order_item_id”
[“must_exist_meta_keys”:protected]=>
array(0) {
}
}
[“stores”:”WC_Data_Store”:private]=>
array(20) {
[“coupon”]=>
string(24) “WC_Coupon_Data_Store_CPT”
[“customer”]=>
string(22) “WC_Customer_Data_Store”
[“customer-download”]=>
string(31) “WC_Customer_Download_Data_Store”
[“customer-download-log”]=>
string(35) “WC_Customer_Download_Log_Data_Store”
[“customer-session”]=>
string(30) “WC_Customer_Data_Store_Session”
[“order”]=>
string(23) “WC_Order_Data_Store_CPT”
[“order-refund”]=>
string(30) “WC_Order_Refund_Data_Store_CPT”
[“order-item”]=>
string(24) “WC_Order_Item_Data_Store”
[“order-item-coupon”]=>
string(31) “WC_Order_Item_Coupon_Data_Store”
[“order-item-fee”]=>
string(28) “WC_Order_Item_Fee_Data_Store”
[“order-item-product”]=>
string(32) “WC_Order_Item_Product_Data_Store”
[“order-item-shipping”]=>
string(33) “WC_Order_Item_Shipping_Data_Store”
[“order-item-tax”]=>
string(28) “WC_Order_Item_Tax_Data_Store”
[“payment-token”]=>
string(27) “WC_Payment_Token_Data_Store”
[“product”]=>
string(25) “WC_Product_Data_Store_CPT”
[“product-grouped”]=>
string(33) “WC_Product_Grouped_Data_Store_CPT”
[“product-variable”]=>
string(34) “WC_Product_Variable_Data_Store_CPT”
[“product-variation”]=>
string(35) “WC_Product_Variation_Data_Store_CPT”
[“shipping-zone”]=>
string(27) “WC_Shipping_Zone_Data_Store”
[“webhook”]=>
string(21) “WC_Webhook_Data_Store”
}
[“current_class_name”:”WC_Data_Store”:private]=>
string(32) “WC_Order_Item_Product_Data_Store”
[“object_type”:”WC_Data_Store”:private]=>
string(18) “order-item-product”
}
[“meta_data”:protected]=>
array(0) {
}
}
}
NULL
string(0) “”

This new feature may be a blessing for some, but the way it was implemented is very very wrong

First, it is rolled out in an update, but this is a major change that should not be hidden. WordPress update release notes contain hundreds of small mostly code-geek notes. Finding a major feature like this is not something a casual web site admin has time for.

Second, there is an existing media size dialog in Settings/Media. Here there are three sizes: Thumbnail, Medium, and Large sizes. These sizes have been around some years, and as a developer, I expect these to be adhered to. However, many plugins have their own image sizes, and the system has not enforced these limits.

In my case I carefully control image sizes and compression using a plugin. All my images are well under the WP maximum – except one, which is intended as a printable 300 dpi image. This image is tied to other data that is added and is dependent on the size of the image WHEN designed. I just spent 2 hours looking for why this was broken.

The CORRECT way to implement this would have been to ADD a new field to the Settings/Media/Image Sizes list: MAXIMUM SIZE. This should have bene set to NONE for existing installs upon upgrade. Admins could then update the value at their discretion. Add advisory text – “WP best practice … ”

Instead of a user-friendly rollout, it’s a geek friendly rollout. And while instructions for overriding the maximum with a function are available, the policy was implemented with a break-and-fix strategy and a hidden rule.

It would have not required much effort to put this in the admin backend with the rules that an admin has every reason to believe are the real rules.

I am the bearer of bad news.
After considerable effort I have diagnosed this, and you cannot fix it.

What is happening is Amazon denies API access to accounts without sales in the last 30 days.

Refer to this page for more information
https://docs.aws.amazon.com/AWSECommerceService/latest/DG/TroubleshootingApplications.html#EfficiencyGuidelines

Once locked out, you must use their new STRIPE method that will give you six templates to build ads from.

This clearly is aimed at pushing out small stores.

Still broken for me. Ads do not appear at all. Pages show the code. I get one line of text “Products from Amazon.com”

I was able to lick this problem with lots of time and CSS. Due to theme differences, my solution may not work for you. I wanted more control over the look and sizing, including an oversize full 1280 video window.

In part I had problems because the videos from vimeo live inside iframe with their own CSS we cannot touch.

56.25% is the height relative at width to produce an HD aspect ratio.

Next time around I may just make a custom Vimeography theme by copying and editing one.

Update – cannot get import to work properly. In my offline test site I deactivated all plugins except WpForms. I disabled my functions file. I switched my theme to TwentySeventeen.

I made a new export. Visually the .json file looks good, but I do not know what to look for. The exported form has 17 fields.

I imported. The imported form has 0 fields.

Update – I loaded my test site and exported the forms. On import to the live site they were blank. I imported one to the test site, it was blank.

Additional information: I was working with WpForms 1.4.6. This happened TWICE – two forms were destroyed. Since then I upgraded to 1.4.72.

At first I thought it was an issue only with column display, so I opened a support ticked (no response). Then I discovered the actual fields were erased so I opened a second support ticket (no response). I turned off a few plugins, but forms did not restore so I turned them back on. We are a large site running many plugins.

Today I made a new form in 1.4.72 with five fields. I did not create any entries (so this condition was not tested). Then edited the columns. I did this twice, I added four fields (9 total). I edited the columns again. The issue was not reproduced. This suggests problem was fixed in after 1.4.6 or was perhaps a bad write to the SQL.

The lingering question: can I restore the damaged forms from an SQL or site backup?

I realized I was basing my two gallery types on different themes. So I thought I could just remove the gallery numbered claw and reference the theme. But the customizations to the gallery were interfering.

So I ended up having to reference the four galleries by number in about s dozen CSS calls

Btw this was only really needed because the plsylister was not paging my 78 videos. I broke it into 4 galleries of 26 (one for expansion)

LOL and the manual says :

Known Issues
None

This is a huge usability issue. I cannot disable the other plug-in as all my pages depend on it – so I cannot preview my product ads!

I have found that other mice editors works.
Clearly this is an issue of Amazon not playing nice with other plugins that add capabilities to the editor. The other guys play nice with each other. Therefore I am sure it is an AALB coding issue.

Clearly AALB is not registering the position its menu controls require without considering who is already loaded. Ninja Forms and WP Forms play nice with Visual Builder from UNYSON/ThemeFuse.

My work-around is to edit this in a non-page/non-post text-box editor and copy/paste. Ugghly

AALB needs to come with a widget tool.

• This reply was modified 7 years, 9 months ago by isaaa. Reason: details added

@belgian-foodie Thanks for info!

Suppose i want ONE ad to appear in every country.
So I register as an associate in each country, and log my associate ID for each country and set the marketplaces….

If I have 6 countries, do I need a separate shortcode for each of the 6 countries? Does the shortcode only display if the user is in that country?

How do I handle countries not listed? Even if there is no associate account available, I need my site users to find our textbook.

Thanks!

• This reply was modified 7 years, 9 months ago by isaaa.

@bazajaytee

I would not call it “user error” when three separate registrations are required and it takes this much effort to find them all. The process is not clearly documented, and their program should only require one registration.

Thank you for your post I spent hours looking for how to solve this problem,and your post solved it in 1 second.

I have same problem and have followed all the instructions at
Manage Your Account.

I must say your AWS / IAM, Product Advertising API documentation is confusing and seems circular. Why two registrations? Or is it three?

AALB complains I have not registered my AWS Access key as an Amazon Associate. Both accounts are using the same email. There is only one email.

I generated the access keys and entered the keys, and the Amazon Associates tracking ID.

So where or how do I tie these together?

Please provide step by step instructions – the docs are not good.

the problem was another plug-in using mustache declared a class “Mustache Autoloader”. Amazon ALB declares same class name.

I deactivated the first plugin, activated Link Builder, and re-activated first plugin

since AALB is Beta, someone should look at this and see if the class name can be more unique.

reporting issue to othr plugin developer