fabinhoalmeida

Here the same technical problem with the classic editor after updating to version 6.7. Most posts assume the default category instead of the category selected by the user writer.

Here the same technical problem with the classic editor after updating to version 6.7. Most posts assume the default category instead of the category selected by the user writer.

Here the same technical problem with the classic editor after updating to version 6.7. Most posts assume the default category instead of the category selected by the user writer.

See the problem in the html of the mobile version of this post (curiously it does not occur in the desktop version):
https://www.areavip.com.br/famosos/mavie-filha-de-neymar-aappear-puxando-o-cabelo-de-carol-dantas-em-foto-e-bruna-biancardi-nao-perdoa- she loves/

Will that be it?

So let me answer a question, Ahmed: Why does only the design three theme need an application id for the Facebook share button?

… I don’t know if this is what causes this behavior, which only occurs with design three: even when logged in as a regular Facebook user, the option to share on a page that I manage does not appear, for example. Through this same share button in the Swift design for example, the option is offered. I believe that for some reason there is a difference in the method of communicating with Facebook between the plugin themes.

• This reply was modified 1 year, 2 months ago by fabinhoalmeida.
• This reply was modified 1 year, 2 months ago by fabinhoalmeida.

Hello

Strangely, the problem only occurs when I’m using Facebook as a user of our page’s property, through the Chrome browser. Logged in with my personal user, the problem does not happen.

Hi!

Yes, we are using the OneSignal plugin

Hello Ahmed.

See below by accessing the published post. Just try to share using the Facebook button and the error will be displayed in the sharing window.

https://tinyurl.com/4uuhzve2

Hello dears,
I’m also having slowness issues on WordPress when the Super PWA plugin is activated. Using Query Monitor I see errors related to the plugin in HTTP API Calls related to the OneSignal notification plugin see:

HEAD https://www.url.com/OneSignalSDKWorker.js.php 404 Not Found
superpwa_file_exists()
wp-content/plugins/super-progressive-web-apps/functions/common.php:176
superpwa_generate_sw()
wp-content/plugins/super-progressive-web-apps/public/sw.php:132
superpwa_upgrader()
wp-content/plugins/super-progressive-web-apps/admin/basic-setup.php:202
do_action(‘admin_init’)
wp-includes/plugin.php:517
Plugin: super-progressive-web-apps 0.0 kB 5 0.0345

HEAD https://www.url.com/OneSignalSDKWorker.js.php cURL error 28: Operation timed out after 5000 milliseconds with 0 bytes received
superpwa_file_exists()
wp-content/plugins/super-progressive-web-apps/functions/common.php:176
superpwa_sw_status_cb()
wp-content/plugins/super-progressive-web-apps/admin/admin-ui-render-settings.php:556
do_settings_fields()
wp-admin/includes/template.php:1824
do_settings_sections()
wp-admin/includes/template.php:1778
superpwa_admin_interface_render()
wp-content/plugins/super-progressive-web-apps/admin/admin-ui-render-settings.php:807
do_action(‘toplevel_page_superpwa’)
wp-includes/plugin.php:517
Plugin: super-progressive-web-apps 5 5.0009

How can this be adjusted?
Thanks

Hi Ahmed,

Thanks for the support.

Of course, here’s the file:

https://drive.google.com/file/d/1fegmNPDDj1JWNO0RqhZC50K9FRTgjgYQ/view?usp=sharing

I’m waiting for you!

Thanks

luckyna,

I tried again and now it’s working normally.

Thank you very much for your support and attention.

Hi Luckyna,

Fortunately, posting web stories is now working normally!!! Thanks!!!

However, the stories archive remains problematic. I tried the procedure you suggested, but when reverting to default it doesn’t work as it should pointing to ‘../web-stories/’, it just keeps pointing to the created itself.

Any suggestions?

Hi Luckyna,

First, thank you for your support.

1. Unfortunately not. It is only accessible to the preview when in draft via url: https://www.url.com/?post_type=web-story&p=800928&preview=true#development=1 . But not through the published permalink. When published, it becomes inaccessible resulting in a 404 page (which in our installation is configured to redirect to the home page)
2. We have already tried republishing this way and also duplicating and publishing, but the behavior remains the same resulting in a 404 page error.
3. I sent the form with all the requested information.

I hope you can help us. We are looking forward to having our stories content normally available..

Thanks!

Hello Ahmed

This time I didn’t quite understand your orientation. If you are going to clear the server’s cache, this was already done in our tests and did not benefit from solving the problem. I await your more detailed guidance so that we can carry out your request. Thanks

Hello Ahmed

Yes of course! The theme we currently use is Newspaper/TagDiv. However, for information, we have already tested the plugin active only with the default WordPress theme, and the problem still appears.

I look forward to your new assessment of the problem.

Thanks