How TDS Classic Controls Item Deployment, Updates, and Deletions in Sitecore

·1 views

TDS Classic uses three deployment settings — Item Deployment, Child Item Synchronization (CIS), and Recursive Deploy Action (RDA) — to determine how items are handled in a target Sitecore database during a deploy. Item Deployment is a per-item property that controls whether an individual item is created, overwritten, or skipped, without affecting its siblings or descendants. CIS determines how deep TDS scans a parent item's descendants, acting as a gate for RDA, which governs what happens to Sitecore items not present in the project. These settings operate on different axes and never overlap, meaning misconfigurations can cause unexpected outcomes such as templates being overwritten or deletions not reaching the web database. The behavior described applies to TDS Classic 6.x on Sitecore 10.x, as well as late TDS 5.x releases.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

WordPress 7.0 prep: PHP version, block themes, and plugin checks to do now

WordPress 7.0 is expected to raise the minimum PHP requirement to 8.0 or later, up from the current 7.2 minimum in WordPress 6.6, putting sites still on PHP 7.x at risk of plugin and theme breakage. Developers are advised to verify their server's PHP version and audit plugins that haven't been updated recently, as these are most likely to fail due to stricter PHP 8.x type handling. The upcoming release is also expected to push Block Themes further to the forefront, leaving Classic Theme sites increasingly behind on new features and plugin compatibility, even if they don't break outright. Site owners are encouraged to identify whether their themes are Classic or Block, and to assess migration costs separately from the core upgrade decision. Treating the core update and theme architecture migration as distinct steps is recommended to make it easier to isolate the cause of any issues that arise.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Egyptian Developer Launches OpenAgentFlow to Simplify Multi-Agent AI Workflow Design

Software engineer AbdulRahman Elzahaby from Egypt has released OpenAgentFlow, an open-source specification language for defining multi-agent AI workflows. The project addresses a gap he identified between visual low-code tools like n8n and code-heavy frameworks like LangGraph, both of which he found limiting during his own automation work. OpenAgentFlow uses a human-readable .oaf file format that describes stateful, multi-agent communication flows independently of any specific execution framework. The approach is modeled on how OpenAPI standardizes REST API descriptions, allowing developers to define complex workflows in compact, portable specification files. A sample customer support triage workflow is demonstrated in just 40 lines of .oaf code, illustrating the tool's aim to reduce repetitive boilerplate.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

HackMIT Contestant Reverse-Engineered a Puzzle's Hidden Model Using 10,000 API Calls

A participant at HackMIT tackled a face-customization puzzle called Face Value, which required finding an avatar configuration that met four simultaneous conditions, including a confidence score of at least 99.9%. Initial manual testing of sliders revealed some patterns but stalled around 60–77% confidence, as the puzzle's scoring model relied on complex multi-feature interactions. The breakthrough came when the contestant used Chrome DevTools to extract the underlying JSON API endpoint, enabling automated querying at hundreds of iterations per minute instead of one per minute by hand. They then applied simulated annealing, coordinate descent, and random restarts to systematically search the configuration space across roughly 10,000 API calls. The project illustrates how reverse-engineering a hidden interface and applying data science techniques can transform an apparently simple UI puzzle into a tractable optimization problem.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer's Own CI Rule Flags Their Explanation of That Same Rule on Day One

A developer building a documentation linter for their project discovered that 47 documents already violated their own 45-line rule, including a 1,203-line offender, before CI was even active. Rather than creating an ignore list or fixing all violations upfront — both seen as traps that delay enforcement or freeze progress — they designed the checker to flag only files that grew longer in a given pull request, not pre-existing violations. This approach uses git's merge-base comparison to avoid creating a second source of truth and to prevent penalizing contributors who make small, unrelated fixes. The rules file itself had to be split into eight separate documents to comply with the very standard it defined. On the first real run, CI flagged the developer's own file mid-edit — the doc explaining the new growth-detection rule had just crossed 46 lines.

0 comments Read more at DEV Community