Bad Schema after Migration

Hi @websgt,

The dropdown box needs an ajax request. An empty listbox is usually the result of an ajax issue. Can you check please?

When you open the inspector, click the Network tab and then edit your publication, look for a request that starts with: admin-ajax.php

Do you see any messages?

Thanks,
Peter

Hi Peter,

When you open the inspector, click the Network tab

Where do I find the inspector? I do not see a Network tab anywhere in your dashboard.

What am I missing?

Thanks?

Hi @websgt,

Sorry! I should have mentioned. ??

The inspector is a browser feature. When you right click somewhere in your browser you’ll see a menu. Search for something like “inspect” or “inspector” (each browser has its own implementation). Click the inspector. Then click on the Network tab. This tab allows you to view requests send from the current page.

Is there a public URL I can visit? Please use the contactform on the plugin website if you prefer to share information in private.

Thanks,
Peter

Hi,

More or less same problem here. “Table/View Name” dropdown is empty in Data Publisher page.
Requests look fine but console is displaying the following error:
Uncaught Error: Syntax error, unrecognized expression: #pub_schema_name option[value=wp_domain.tld]

https://snipboard.io/Qf3wJY.jpg

Thanks!

Hi @luk4,

Thanks for the detailed error message. When do you get this error? Do you have a database named wo_domain.tld? Are you on the free on premium version?

Thanks,
Peter

Hi,

Thanks for your quick reply.

I got it when on page loading after clicking on “Create publication” button, in “Publications” tab. Technically, when requesting /wp-admin/admin.php?page=wpda_publisher with following POST data: `table_name=wp_wpda_publisher
action=new`

Yes, the database name see in the error is correct. Other WPDA function is working great with this database.

I’m conducting a few tests with the free version.

EDIT: The console error is a simple jQuery selector error because the dot in the db name used as value in the dropdown option field. Putting the db name between simple quotes fix it: jQuery("#pub_schema_name option[value='wp_domain.tld']") (note the simple quotes) instead of jQuery("#pub_schema_name option[value=wp_domain.tld]") (no simple quotes)

https://snipboard.io/xDnor2.jpg

EDIT 2: https://mathiasbynens.be/notes/unquoted-attribute-values ??

• This reply was modified 2 years, 11 months ago by Anonymous User 20348352.
• This reply was modified 2 years, 11 months ago by Anonymous User 20348352.
• This reply was modified 2 years, 11 months ago by Anonymous User 20348352.
• This reply was modified 2 years, 11 months ago by Anonymous User 20348352.

Peter,

You have been to my sight before. I just sent a password reset to you.

Thanks,
Steve

Hi @luk4,

Thank you for the detailed explanation ?? and the solution as well! ?? I will fix this asap. Just wondering: which browser are you using? So far I have not been able to reproduce this issue. It would be great to have a test case to check whether my updates work.

Thanks,
Peter

Hi Steve,

>>> You have been to my sight before.

I know! ??

Same issue, different cause. You are on bluehost. They install and activate their own plugin by default. That plugin kills all our ajax requests. When disabled, the Data Publisher works as expected.

Be careful with caching plugins. Some caching plugins seem to even cache requests that should not be cached.

Best regards,
Peter

You’re welcome! ??

I’m using Firefox Developer Edition (v.99). But I’ve the exact same error with Chromium (v.100).

Just so you know, I patched wp-data-access/WPDataAccess/Data_Publisher/WPDA_Publisher_Form.php (lines 908-910) as mention earlier and I confirm the whole issue is fixed on my end:

function updateWordPressDatabaseName() {
					jQuery("#pub_schema_name option[value='<?php 
        echo  esc_attr( $wpdb_name ) ;
        ?>']").text("WordPress database (<?php 
        echo  esc_attr( $wpdb_name ) ;
        ?>)");
				}

But feel free to drop a patched version to let me try before releasing it if needed.

Thank you @luk4,

I tested with Chrome, Firefox, Edge and Safari on Linux, Windows and Mac OS: no issues! ?? I’ll fix it anyway, but still strange I can’t reproduce this issue. What OS are you on?

Thanks,
Peter

That’s really weird. Are you sure you have a dot in the DB name used as value of option field? Here is a dumb demo: https://codepen.io/c88f8f957604d056506a80/pen/ZEvXMOr

I use Arch btw. But as the link shared earlier indicates:

So, a valid unquoted attribute value in CSS is any string of text that is not the empty string, is not just a hyphen (-), consists of escaped characters and/or characters matching /[-_\u00A0-\u10FFFF]/ entirely, and doesn’t start with a digit or two hyphens or a hyphen followed by a digit.

Which doesn’t include dots.

You can also check selectors here: https://mothereff.in/unquoted-attributes

Cheers,

• This reply was modified 2 years, 11 months ago by Anonymous User 20348352.

Hi @luk4,

>>> Are you sure you have a dot in the DB name used as value of option field?

Absolutely! My magic PC handles this with and without the quotes. ??

I’m greatful for your feedback anyway! I’ll change it with the update.

Have a nice weekend,
Peter