joydipkar73

no sir, this is not working

for AMP, you need to put AMP ad code in the plugin. AMP ad codes are different from normal ad codes.
for that you may find this link useful https://adinserter.pro/documentation/amp-pages
this same trick will work for the free version as well. all you need is to generate the amp version of the ad code.

you can hide the button using woocommerce or cpo setting

that can easily be done by using inspector in browser.
i did one such order:
check this

• This reply was modified 3 years, 12 months ago by joydipkar73.

please ignore the above scenarios.
The steps and outcomes are as follows:
1. I upload the image -> it appears everywhere correctly.
2. I move the image to trash-> image goes to trash
3. I delete the image from trash -> image deleted from bucket. But remains in trash and 404 fatal error is shown.

it can not delete even if the image exists in the bucket.
i have to move to trash and then i can not delete it. the same 404 fatal error is being shown.

I could make it work by creating new api key on google console. after deactivating the old key was not working.
but the image-404 error is still giving if the image is deleted directly from bucket.

No, it is now giving a different problem.

6901Mother.jpg
Post-processing of the image failed likely because the server is busy or does not have enough resources. Uploading a smaller image may help. Suggested maximum size is 2500 pixels.

But the image is being uploaded to local media library. But my setting is to serve from bucket only, no local files.

Also, if the image does not exists in the bucket then I get the error:

Fatal error: Uncaught Exception: {"error":{"code":404,"message":"No such object: stateless-afterfantasy-com/6901Mother-1-188x300.jpg","errors":[{"message":"No such object: stateless-afterfantasy-com/6901Mother-1-188x300.jpg","domain":"global","reason":"notFound"}]}}
in /var/www/vhosts/afterfantasy.com/httpdocs/wp-content/plugins/wp-media-storage-to-cloud/vendor/google/cloud-core/src/RequestWrapper.php on line 368

Call stack:

Google\C\C\RequestWrapper::convertToGoogleException()
wp-content/plugins/wp-media-storage-to-cloud/vendor/google/cloud-core/src/RequestWrapper.php:207
Google\C\C\RequestWrapper::send()
wp-content/plugins/wp-media-storage-to-cloud/vendor/google/cloud-core/src/RestTrait.php:97
Google\C\S\C\Rest::send()
wp-content/plugins/wp-media-storage-to-cloud/vendor/google/cloud-storage/src/Connection/Rest.php:192
Google\C\S\C\Rest::deleteObject()
wp-content/plugins/wp-media-storage-to-cloud/vendor/google/cloud-storage/src/StorageObject.php:185
Google\C\S\StorageObject::delete()
wp-content/plugins/wp-media-storage-to-cloud/admin/channels/class-w2cloud-gcs-process.php:98
w2cloud_GCS_Process::gcs_delete_object()
wp-content/plugins/wp-media-storage-to-cloud/admin/class-w2cloud-media-control.php:229
w2cloud_media_control::w2cloud_delete_media()
wp-includes/class-wp-hook.php:289
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:311
WP_Hook::do_action()
wp-includes/plugin.php:484
do_action()
wp-includes/post.php:5940
wp_delete_attachment()
wp-admin/upload.php:194

oh! i see.
thanks for pointing out.

No, the problem persists.
When WP-stateless were active the setting was to serve everything fully from cloud.
That time images were ok in storage.
But after I synced the images using your plugin, they have been overwritten to zero bytes files as it assumed that images to be synced are there in media library already!! But actually they were not!! Therefore based on the above assumption, your plugin is creating a new file with the same name as in media library listing but after that finding the image does not exists, it closes the file and saves. When it should have aborted.

Is the above a right explanation?

• This reply was modified 4 years, 1 month ago by joydipkar73.

View post on imgur.com

View post on imgur.com

yes. the errors disappeared.
thanks.

Also, I notice one thing.
Whenever I submit content from the front end, a ‘0’ is appended at the end of the content when I open it from admin panel for editing.

Could you please take a look?

Thanks for the update.
As the page I am using is internal ie, login needed therefore it will not affect any SEO so far. It is expected.
BUT the biggest problem which I would suggest you to inspect is :
I selected in the page “AMP Disabled”, therefore AMP should be disabled in the particular page and it should work fine.
Though the reality is a bit different, because I had to disable the full page template ie, for all the pages (!!!) to get desired result.
Could you please investigate this issue that why in the page setting “AMP Disabled” is not working?