Jump to content

USPS RATE


Guest BaggBoy

Recommended Posts

Guest BaggBoy

I received this email from USPS, don't know if this will impact shipping mods in CC, but thought I'd share it.

Dear Customer,

On May 14 2007, the United States Postal Service® will implement

changes for Domestic Mail. In response to these changes, a new Domestic

Rates Application Program Interface (API), RateV3, will be released by

USPS Web Tools®.

A staging environment will be available to test the new API on April

19th. Please go to:

http://stg-production.shippingapis.com/

<http://stg-production.shippingapis.com/>

RateV2 will still be available after the release of RateV3, and will

suffice unless rates need to be calculated for Large Priority Mail

packages. USPS is introducing a new dimensional weight pricing model for

Large Priority Mail pieces. Dimensional weighting is a mechanism that

converts the cubic size of a piece into a weight. If a large box is very

light, it will be charged as a higher-weight piece, based on the

International Air Transport Association (IATA) standard. This change

only affects Priority Mail pieces larger than 1 cubic foot, and

traveling to destinations within zones 5-8. The Rate V3 API still

requires dimensions if an item is large, regardless of the zone.

To capture the dimensional weight for Large Priority Mail pieces, RateV3

will require three new dimension tags for rectangular Priority Mail

pieces: Length, Width, and Height; and four new dimension tags for

non-rectangular pieces: Length, Width, Height, and Girth. Shippers will

specify in the existing Container tag whether a Large Priority Mail

piece is rectangular or non-rectangular.

RateV3 also implements changes to First Class Mail. A new tag, First

Class Mail Type, will be used to specify whether a First Class Mail

piece is a letter, flat, or parcel. Today, First Class Mail pieces are

charged identical rates, regardless of the type of package. With the

change, the postage for each type of First Class Mail piece will more

accurately reflect the processing costs for each. The Machineable tag

will also be applied to First Class Mail, in addition to Parcel Post.

An example of an XML request of the Rate V3 is:

<RateV3Request USERID="000AAAAA9999">

<Package ID="1ST">

<Service>FIRST CLASS</Service>

<FirstClassMailType>LETTER</FirstClassMailType>

<ZipOrigination>44106</ZipOrigination>

<ZipDestination>90210</ZipDestination>

<Pounds>0</Pounds>

<Ounces>0.75</Ounces>

<Size>REGULAR</Size>

<Machinable>false</Machinable>

</Package>

<Package ID="2ND">

<Service>PRIORITY</Service>

<ZipOrigination>44106</ZipOrigination>

<ZipDestination>20770</ZipDestination>

<Pounds>5</Pounds>

<Ounces>8</Ounces>

<Container>NONRECTANGULAR</Container>

<Size>LARGE</Size>

<Width>15</Width>

<Length>30</Length>

<Height>15</Height>

<Girth>55</Girth>

</Package>

<Package ID="3RD">

<Service>ALL</Service>

<ZipOrigination>90210</ZipOrigination>

<ZipDestination>20770</ZipDestination>

<Pounds>8</Pounds>

<Ounces>32</Ounces>

<Container>RECTANGULAR</Container>

<Size>LARGE</Size>

<Width>15</Width>

<Length>30</Length>

<Height>15</Height>

<Machinable>true</Machinable>

</Package>

</RateV3Request>

Link to comment
Share on other sites

Hmm. Sounds like another change would be needed going by that e-mail. Errrrr.

Each product might need it's own packaging size now, for at least items that require packaging over 1 cubic ft.

Thanks for the heads up.

Link to comment
Share on other sites

Guest conspicuouschick

I recieved something similar which I'll copy/paste below, but my question is - does that mean we, as CC users, will have to go in and modify the code on the module? In other words, is this going to be another thing that should be fixed by the developers but won't - at least not in time?

Dear Customer,

On May 14, 2007, the United State Postal Service will implement changes in accordance with the Federal Register, to adjust postage prices to cover operational costs and respond to changes in the marketplace.

The Postal Service will be implementing the rebranding of its international product line. A staging environment will be available to test the new Application Program Interfaces (APIs) along with a User Guide, starting April 19th. To test, please go to:

http://stg-production.shippingapis.com/

https://stg-secure.shippingapis.com/

The rebranding effort will align our international products with our well-known and trusted domestic products – Express Mail, Priority Mail, and First Class Mail. Below are explanations as to how each existing international API will be affected by these changes.

Global Label Express and Global Express Mail V2

A new API (‘ExpressMailIntl’) will be implemented as part of the rebranding. ‘ExpressMailIntl’ will mirror the schema of the current Global Label Express with the following changes:

1. All references to Global Label Express will be altered to show Express Mail International.

2. A new Flat Rate Envelope option will be available via the existing Container tag.

3. A new PO Box tag will be available to indicate that an international address is a Post Office Box.

4. The To Phone will only be required if the International Address is flagged as a PO Box.

5. There will be a new Merchandise option available via the Content Type tag.

6. When the Non-Delivery Option tag in the response indicates Redirect, the Alternate Return Country tag must equal the To Country value.

7. The SDR (Special Drawing Rights) Value will be removed from the request but will be returned in the response, based on the Value of Contents sent in the request.

8. A required “Agreement†tag must be included in the ExpressMailIntl request. This tag will indicate whether or not the shipper has agreed to the Customs Information and will provide for an electric signature.

9. After May 13th, Global Express Mail V2 API will no longer be available.

An example of an XML request of the Express Mail International API is below.

<ExpressMailIntlRequest USERID="x">

<Option/>

<ImageParameters/>

<FromFirstName>a</FromFirstName>

<FromMiddleInitial>a</FromMiddleInitial>

<FromLastName>a</FromLastName>

<FromFirm>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromFirm>

<FromAddress1>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromAddress1>

<FromAddress2>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromAddress2>

<FromUrbanization>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromUrbanization>

<FromCity>a</FromCity>

<FromState>aa</FromState>

<FromZip5>00000</FromZip5>

<FromZip4>0000</FromZip4>

<FromPhone>0000000000</FromPhone>

<FromCustomsReference>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromCustomsReference>

<ToName>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToName>

<ToFirm>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToFirm>

<ToAddress1>a</ToAddress1>

<ToAddress2>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToAddress2>

<ToAddress3>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToAddress3>

<ToCity>a</ToCity>

<ToProvince>aaaaaaaaa</ToProvince>

<ToCountry>Italy</ToCountry>

<ToPostalCode>aaaaaaaaa</ToPostalCode>

<ToPOBoxFlag>Y</ToPOBoxFlag>

<ToPhone>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToPhone>

<ToFax>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToFax>

<ToEmail>[email protected]</ToEmail>

<ToCustomsReference>aaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToCustomsReference>

<NonDeliveryOption>ABANDON</NonDeliveryOption>

<AltReturnAddress1></AltReturnAddress1>

<AltReturnAddress2></AltReturnAddress2>

<AltReturnAddress3></AltReturnAddress3>

<AltReturnAddress4></AltReturnAddress4>

<AltReturnAddress5></AltReturnAddress5>

<AltReturnAddress6></AltReturnAddress6>

<AltReturnCountry></AltReturnCountry>

<Container>VARIABLE</Container>

<ShippingContents>

<ItemDetail>

<Description>a</Description>

<Quantity>2</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber>0</HSTariffNumber>

<CountryOfOrigin>Morocco</CountryOfOrigin>

</ItemDetail>

<ItemDetail>

<Description>a</Description>

<Quantity>2</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber>0</HSTariffNumber>

<CountryOfOrigin>Palau</CountryOfOrigin>

</ItemDetail>

<ItemDetail>

<Description>a</Description>

<Quantity>2</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber>0</HSTariffNumber>

<CountryOfOrigin>Iceland</CountryOfOrigin>

</ItemDetail>

</ShippingContents>

<InsuredNumber>aaaaaaaaaaaaaaaaaaaaaaaaaaaa</InsuredNumber>

<InsuredAmount/>

<Postage/>

<GrossPounds>3</GrossPounds>

<GrossOunces>0</GrossOunces>

<ContentType>MERCHANDISE</ContentType>

<ContentTypeOther>aaaaaaaaaaaaaaa</ContentTypeOther>

<Agreement>Y</Agreement>

<Comments>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</Comments>

<LicenseNumber>aaaaaaaaaaaaaaaaaaaaaaaa</LicenseNumber>

<CertificateNumber>aaaaaaaaaaaaaaaaaaaaaaaa</CertificateNumber>

<InvoiceNumber>aaaaaaaaaaaaaaaaaaaaaaaa</InvoiceNumber>

<ImageType>PDF</ImageType>

<ImageLayout>ONEPERFILE</ImageLayout>

<CustomerRefNo>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</CustomerRefNo>

<POZipCode>00000</POZipCode>

<LabelDate></LabelDate>

<EMCAAccount/>

<EMCAPassword/>

<HoldForManifest>N</HoldForManifest>

</ExpressMailIntlRequest>

Global Label Airmail and Global Label Priority Large Flat Rate Envelope

A new API (‘PriorityMailIntl’) will be implemented as part of the rebranding. ‘PriorityMailIntl’ will mirror the schema of the current Global Label Airmail with the following changes:

1. All references to Global Airmail Parcel Post will be altered to show Priority Mail International.

2. A new Flat Rate Box option will be available via the existing Container tag.

3. The existing Global Priority Mail Large Flat Rate Envelope will be available via the Container tag of the new Priority Mail International API (this option will follow the 4 pound/$400 limits of the current Global Label Priority API).

4. A new PO Box tag will be available to indicate that an international address is a Post Office Box.

5. The To Phone tag will only be required if the International Address is flagged as a PO Box.

6. There will be a new Merchandise option available via the Content Type tag.

7. When the Non-Delivery Option tag in the response indicates Redirect, the Alternate Return Country tag must equal the To Country tag (not applicable when the Container is Flat Rate Envelope).

8. The SDR (Special Drawing Rights) Value tag will be removed from the request but will be returned in the response, based on the Value of Contents sent in the request.

9. A required “Agreement†tag must be included in the ExpressMailIntl request. This tag will indicate whether or not the shipper has agreed to the Customs Information.

10. After May 13th, Global Label Priority Mail API will no longer be available.

An example of an XML request of the Priority Mail International API is below.

<PriorityMailIntlRequest USERID="x">

<Option/>

<ImageParameters/>

<FromFirstName>a</FromFirstName>

<FromMiddleInitial>a</FromMiddleInitial>

<FromLastName>a</FromLastName>

<FromFirm>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromFirm>

<FromAddress1>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromAddress1>

<FromAddress2>a</FromAddress2>

<FromUrbanization>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromUrbanization>

<FromCity>a</FromCity>

<FromState>aa</FromState>

<FromZip5>00000</FromZip5>

<FromZip4>0000</FromZip4>

<FromPhone>0000000000</FromPhone>

<FromCustomsReference>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromCustomsReference>

<ToName>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToName>

<ToFirm>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToFirm>

<ToAddress1>a</ToAddress1>

<ToAddress2>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToAddress2>

<ToAddress3>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToAddress3>

<ToCity>a</ToCity>

<ToProvince>aaaaaaaaa</ToProvince>

<ToCountry>Pakistan</ToCountry>

<ToPostalCode>aaaaaaaaa</ToPostalCode>

<ToPOBoxFlag>Y</ToPOBoxFlag>

<ToPhone>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToPhone>

<ToFax>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToFax>

<ToEmail>[email protected]</ToEmail>

<ToCustomsReference>aaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToCustomsReference>

<NonDeliveryOption>ABANDON</NonDeliveryOption>

<AltReturnAddress1/>

<AltReturnAddress2/>

<AltReturnAddress3/>

<AltReturnAddress4/>

<AltReturnAddress5/>

<AltReturnAddress6/>

<AltReturnCountry/>

<Container>VARIABLE</Container>

<ShippingContents>

<ItemDetail>

<Description>a</Description>

<Quantity>1</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber>0</HSTariffNumber>

<CountryOfOrigin>Japan</CountryOfOrigin>

</ItemDetail>

<ItemDetail>

<Description>a</Description>

<Quantity>1</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber>0</HSTariffNumber>

<CountryOfOrigin>India</CountryOfOrigin>

</ItemDetail>

<ItemDetail>

<Description>a</Description>

<Quantity>1</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber>0</HSTariffNumber>

<CountryOfOrigin>China</CountryOfOrigin>

</ItemDetail>

</ShippingContents>

<Insured>N</Insured>

<InsuredNumber>aaaaaaaaaaaaaaaaaaaaaaaaaaaa</InsuredNumber>

<InsuredAmount/>

<Postage/>

<GrossPounds>3</GrossPounds>

<GrossOunces>0</GrossOunces>

<ContentType>MERCHANDISE</ContentType>

<ContentTypeOther>aaaaaaaaaaaaaaa</ContentTypeOther>

<Agreement>Y</Agreement>

<Comments>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</Comments>

<LicenseNumber>aaaaaaaaaaaaaaaaaaaaaaaa</LicenseNumber>

<CertificateNumber>aaaaaaaaaaaaaaaaaaaaaaaa</CertificateNumber>

<InvoiceNumber>aaaaaaaaaaaaaaaaaaaaaaaa</InvoiceNumber>

<ImageType>PDF</ImageType>

<ImageLayout>ONEPERFILE</ImageLayout>

<CustomerRefNo>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</CustomerRefNo>

<POZipCode>00000</POZipCode>

<LabelDate></LabelDate>

<HoldForManifest>N</HoldForManifest>

</PriorityMailIntlRequest>

Global Label Priority

A new API (‘First ClassMailntl’) will be implemented as part of the rebranding. In effect, the current Global Priority Mail variable option will no longer be available. Although a completely different international product, ‘FirstClassMailIntl’ will mirror the schema of the current Global Label Priority with the following changes:

1. All references to Global Priority Mail will be altered to show First Class Mail International

2. The existing Large Flat Rate Envelope option will now be available as a Flat Rate Envelope in the Priority Mail International API via the Container type (not via the First Class Mail International API)

3. A new PO Box tag will be available to indicate that an international address is a Post Office Box.

4. The To Phone tag will only be required if the International Address is flagged as a PO Box.

5. There will be a new Merchandise option available via the Content Type tag.

6. A required “Agreement†tag must be include in the ExpressMailIntl request. This tag will indicate whether or not the shipper has agreed to the Customs Information.

7. The label is now single ply, 4 inches by 6 inches.

An example of an XML request of the First Class Mail International API is below.

<FirstClassMailIntlRequest USERID="x">

<Option/>

<ImageParameters/>

<FromFirstName>a</FromFirstName>

<FromMiddleInitial>a</FromMiddleInitial>

<FromLastName>a</FromLastName>

<FromFirm>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromFirm>

<FromAddress1>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromAddress1>

<FromAddress2>a</FromAddress2>

<FromUrbanization>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</FromUrbanization>

<FromCity>a</FromCity>

<FromState>aa</FromState>

<FromZip5>00000</FromZip5>

<FromZip4>0000</FromZip4>

<FromPhone>0000000000</FromPhone>

<ToName>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToName>

<ToFirm>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToFirm>

<ToAddress1>a</ToAddress1>

<ToAddress2>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToAddress2>

<ToAddress3>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToAddress3>

<ToCity>a</ToCity>

<ToProvince>aaaaaaaaa</ToProvince>

<ToCountry>France</ToCountry>

<ToPostalCode>aaaaaaaaa</ToPostalCode>

<ToPOBoxFlag>N</ToPOBoxFlag>

<ToPhone>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToPhone>

<ToFax>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</ToFax>

<ToEmail>[email protected]</ToEmail>

<ShippingContents>

<ItemDetail>

<Description>a</Description>

<Quantity>1</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber/>

<CountryOfOrigin/>

</ItemDetail>

<ItemDetail>

<Description>a</Description>

<Quantity>1</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber/>

<CountryOfOrigin/>

</ItemDetail>

<ItemDetail>

<Description>a</Description>

<Quantity>1</Quantity>

<Value>1.0</Value>

<NetPounds>0</NetPounds>

<NetOunces>3</NetOunces>

<HSTariffNumber/>

<CountryOfOrigin/>

</ItemDetail>

</ShippingContents>

<Postage/>

<GrossPounds>3</GrossPounds>

<GrossOunces>0</GrossOunces>

<ContentType>MERCHANDISE</ContentType>

<ContentTypeOther>aaaaaaaaaaaaaaa</ContentTypeOther>

<Agreement>Y</Agreement>

<Comments>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</Comments>

<LicenseNumber>aaaaaaaaaaaaaaaaaaaaaaaa</LicenseNumber>

<CertificateNumber>aaaaaaaaaaaaaaaaaaaaaaaa</CertificateNumber>

<InvoiceNumber>aaaaaaaaaaaaaaaaaaaaaaaa</InvoiceNumber>

<ImageType>PDF</ImageType>

<ImageLayout>ONEPERFILE</ImageLayout>

<CustomerRefNo>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</CustomerRefNo>

<LabelDate></LabelDate>

<HoldForManifest>N</HoldForManifest>

</FirstClassMailIntlRequest>

International Rate (IntlRate)

Changes to the International Rate API (IntlRate) will be implemented in response to the International rebranding. The International Rate request will follow the same structural schema, with the addition of one optional tag, ValueOfContents. When ValueOfContents is provided in the request, one of two scenarios will occur in the returned response:

1. An <Insurance> tag reflecting the insurance fee will be returned based on the amount sent in the <ValueOfContents> tag.

2. An <InsComment> tag will be returned displaying one of the following three reasons why insurance is not available:

§ “not available for service†or

§ “not available for destination for service†or

§ “not available for given valueâ€

When applicable an Indemnity tag will also be returned in the response. Indemnity is free of charge with this service and is applicable for Priority Mail International. It will be returned if the Indemnity amount in the response is greater than the Insured Value sent in the request.

As applicable to the rebranding effort, the International Rate API will be modified to return the rebranded international products: Express Mail International, Priority Mail International, and First Class Mail International.

An example of an XML request of the International Rate API is below.

<IntlRateRequest USERID="000AAAAA9999">

<Package ID="1st">

<Pounds>4</Pounds>

<Ounces>3</Ounces>

<MailType>Package</MailType>

<Country>Canada</Country>

</Package>

<Package ID="2nd">

<Pounds>4</Pounds>

<Ounces>3</Ounces>

<MailType>Package</MailType>

<ValueOfContents>500</ValueOfContents>

<Country>Afghanistan</Country>

</Package>

</IntlRateRequest>

If you have any questions, concerns or technical inquiries, please contact the USPS Internet Customer Care Center via email at [email protected] or phone 1-800-344-7779.

Sincerely,

Patti Mason

Manager USPS.com

Link to comment
Share on other sites

9. After May 13th, Global Express Mail V2 API will no longer be available.

What?!?! That doesn't make me warm and fuzzy anymore. :errm:

All USPS users of CubeCart might need an update and FAST!

Link to comment
Share on other sites

Guest conspicuouschick

9. After May 13th, Global Express Mail V2 API will no longer be available.

What?!?! That doesn't make me warm and fuzzy anymore. :errm:

All USPS users of CubeCart might need an update and FAST!

If you use the USPS module, I'm surprised you haven't received one of these emails too.

Obviously I don't hold out much hope this will be taken care of in the manner and expediency it deserves. Shoot, we're all still waiting for a Google Checkout module, and better yet, a Google Base fix since they altered their requirements. So far, nothing.

Link to comment
Share on other sites

Guest BaggBoy

Yeah, I love CC, but sometimes it seems the developers are either sleeping instead of working or they expect a third party mod maker to solve problems. That's my only real gripe with CC, that issues that should be addressed, are not.

Link to comment
Share on other sites

Guest conspicuouschick

Yeah, I love CC, but sometimes it seems the developers are either sleeping instead of working or they expect a third party mod maker to solve problems. That's my only real gripe with CC, that issues that should be addressed, are not.

Exactly. I shouldn't have to pay for a third party mod when the feature was originally part of CC, but they don't seem to care enough to fix it. While google base has been enough of an inconvenience, this is truly panic inducing. How are any of us supposed to do business if the usps module "breaks"? Most of my orders go via first class mail so it would be ridiculous to use another shipping service. What other options do any of us have aside from performing some ritual designed to provoke a solution?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...