Skip to content

add current blog constraint for cloning (WP-953) - #577

Merged
vsolovei-smartling merged 1 commit into
masterfrom
WP-953-cloning-per-blog
Aug 21, 2025
Merged

vsolovei-smartling merged 1 commit into
masterfrom
WP-953-cloning-per-blog

Conversation

@vsolovei-smartling

Copy link
Copy Markdown
Contributor

No description provided.

Comment thread readme.txt
Comment on lines +65 to +67
= 4.3.1 =
* Changed cloning to only work with submissions from the blog that initiates the cron job

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I remember you mentioned that this is some specific to some client setup. But will this still work for any other clients who do not run cron from the specific blog?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This defaults to blog 1 by default, which most clients use as the source

/**
* Looks for submissions with status = 'New' AND batch_uid <> '' AND is_locked = 0
*/
public function findSubmissionForUploadJob(): ?SubmissionEntity

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Obsolete, unused

@vsolovei-smartling
vsolovei-smartling merged commit 930e342 into master Aug 21, 2025
2 checks passed
@vsolovei-smartling
vsolovei-smartling deleted the WP-953-cloning-per-blog branch August 21, 2025 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants