No category and wrong Author after posting

Hello, sorry for posting again but after lot of debugging and being unable to solve, I would like to ask if someone knows an alternative to Postie. This plugin seems to be no longer working when fetching e-mails automatically.

If I try the manual run, it is almost okay. I tried to uninstall this plugin and then install again with no luck. I noticed the database was not cleared after the plugin uninstallation since the settings have been restored once I installed it again. If someone knows how to perform a full removal process would be great!

I don’t understand such NO support at all by Postie developers.

Thanks

Hello,

thank you for replying. Regarding the user, it is linked to the post as expected.
I am definitely using a category, not a custom taxonomy. After the new article creation, I see just a “dash sign” (it’s like a minus) under the category column within the article list (which is different from “no category” as far as I know).

By saying okay I mean that it worked as expected (category is assigned) on manual run. But if I let the scheduled task run every “xx” minutes, I can’t see any category for the new article.

Sorry, I thought there’s no more people supporting this plugin and I was hoping some other user would have some hint. Apologizes, I understand.

Just let me know if I can put some debug log or do any specific test on the source code. Consider that this website is coming from a manual WordPress core upgrade from version 4.2 to 6.1.1.

Hi!

I have some news since I could debug a bit the problem. I can provide you the full log file in case of need but please find the below considerations.

I have category having ID = 10 and tag with ID = 11.
For what I could see, every time I send an e-mail to the configured address,
the batch runs and it creates just one new row into the wp_term_relationships table.
This means that I have one new row with ID 11 only. If I make a comparison to the posts having the category and tag being associated, I see this for the correct posts:

{"object_id":"7174","term_taxonomy_id":"11","term_order":"0"},
{"object_id":"7174","term_taxonomy_id":"10","term_order":"0"},

While I only see this for the new post without the category:

{"object_id":"7182","term_taxonomy_id":"11","term_order":"0"},

I tried to manually insert a new entry into the wp_term_relationships table and could see the post correctly in the Admin panel (meaning that I can see both category and tag set as well as the author). This is equivalent to setting up the category in the admin panel.

Here’s what I could see in the debug logs:
[14-Jan-2023 14:52:06 Europe/Rome] Postie [debug]: Query: INSERT INTO wp_term_relationships (object_id, term_taxonomy_id) VALUES (7182, 11)
Which is okay as reported above.

But I cannot see the other insert instruction for term_taxonomy_id = 10.

The below query raises me a suspect (why is it excluding 10 in the NOT IN clause?):

[14-Jan-2023 14:52:06 Europe/Rome] Postie [debug]: Query: 
			SELECT DISTINCT t.term_id
			FROM wp_terms AS t  INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id
			WHERE tt.taxonomy IN ('post_tag') AND t.term_id NOT IN (10,29,30) AND tr.object_id IN (7182)

I suspect it is something related to a missing database configuration for such category having id = 10 on the core of WordPress but can’t understand which one for now.

Do you have any idea?

Thanks!

• This reply was modified 3 years, 5 months ago by fbcyborg.

Hi @wayneallen-1, stated that it is supposed to be a bug with UAM since if I disable such plugin everything is going ok, I have a question for you: what is the difference between the manual run (which is working well) and the automatic schedule? There should be something different between the two modes otherwise I can’t explain why it works in the first case.

In the meantime I opened an issue on GitHub to the UAM plugin project owner.

thank you

Thank you for replying. I would like to make a test (even changing a bit the source code): is it possible to hardcode username/password in postie so that it believes it is authenticated and go to the “manual mode”?

Another idea I have is to try to track via DEBUG logs all the main flow parts to understand where it fails. It’s weird such problem is happening only in production.

So you also think it could be an idea to install the support addon? Any risk?

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

Thank you!

I made a test setting up Force User Login to Yes but was unsuccessful. I also made sure the e-mail used to send the post had an associated username.

I’m going to install the support addon and let you know.

By the way, I see this red warning at the support addon page: “Please do not install this plugin unless requested to do so.“

Is it sort of dangerous?

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