martin1723

Yes, this is correct. Switching off this WP AIOS option “salt” (WP Security>Miscellaneous / user-security>Tab: Salt) solved the problem.

Thanks for your immediate help.

Martin

Thanks for your quick replay.

I sent you the log-files and a screenshot via the contact form on your site.

Thanks

Martin

I’m having the same issue. No matter what date-time-format I use in the excel-table all imported posts have the same current date+time. In data base the post_date and post_modified are the current datetime of the import.

Is there a specific datetime syntax to use in the excel-cell?

I read a thread on github (regarding wordpress-importer-plugin), which sounds like this could be associated with wordpress-api?? With that plugin they seem to have fixed it. https://github.com/Automattic/wp-calypso/issues/61145#issuecomment-1083596678

Thanks for the quick replay! I’ll contact you for the custom coding.

Hi mbrsolution,
thanks for your quick reply.
As I wanted to do the conflict test today the error was gone. Didn’t change anything. Funny.
There seemed to be only a server-hickup yesterday… ??
Thanks.

I found the solution to the problem by accident.
This morning I updated PHP to 7.3 and the ajax error was gone.

Hi,
thanks for your reply.
I use All In One WP Security plugin. I deactivated it but no change.
Still 1 to 3 tables out of 14 are not displayed in the post because of the ajax error.

You said that something blocks the action=get_wdtable. I understand that in this case all wdtables would be blocked, isn’t it? But there ar only 1 or 2 or 3 tables out of 14 blocked in this post. Other posts with only one or two tables show no error when loading.

To be honest, I don’t know where to look for the reason for blocking the “action=get_wdtable”.
Could you give me a hint?!

Regards
Martin

I found the problem in my table-code.

To force the table column widths I inserted images with the desired column width (i.e. 150px). Even if there goes only text in the table head its better (for me) to create a small png-image with that text and the correct width. Doing so it is also possible to horizontally align the header-text/colour differently from the table content (because its in the image).

What caused the problem with the row-offset?
Browsers handle code-errors obviously different. The one simply ignores the incorrect code, the other one swallows up.
In one case I forgot the second ” whith empty alt-attribute. Another mistake was a missing space between alt=”” and />.

So, the mistakes were all mine… ?? And I learnd that browsers behave differently tolerant.

Thanks Tobias for the good table work!

• This reply was modified 5 years, 7 months ago by martin1723.
• This reply was modified 5 years, 7 months ago by martin1723.

Hi Kshirod,
thank you for fixing the issue. Everything is fine now.
Great and fast support!

For me it doesn’t look ok. I checked it with Chrome and Firefox.
Here are some screenshots: https://drive.google.com/open?id=1gcxXQwYwtfM0a6htyjIa-yxA-lUvOUK5

Hi Tobias,
thanks for the quick reply!
That helped a lot.

Kind Regards
Martin

Hi,
Thanks for your reply. Please read before writing: I have NO TFA installed or activated. And as you didn’t provide a solution, I deleted Captcha.

Best regards
Martin

That’s a good idea. I’ll try this. Danke!

Thanks for your quick response!