TYPO3 Core

I never needed the CE uid till now, so I think it should be handled extension specific.

But if the majority is +1, it should be implemented with FLOW3's FLUID in mind.
Function getContentObject() is v4/6 specific thing because FLOW3 has no content element
and if there would be anything like this, it has no uid, but an identifier.

I understand your concern but isn't extbase a TYPO3 extension and should we be worried about eventually upcoming FLOW3 based projects?
Anyway, what about a more generic, configurable way to retrieve a unique identifier?

Currently a viewHelper already has the uid in its context, but I needed the cObj when working inside partials.

class Tx_MyExt_ViewHelpers_UidViewHelper extends Tx_Fluid_Core_ViewHelper_AbstractViewHelper {

  /**
   * @var Tx_Extbase_Configuration_ConfigurationManagerInterface
   */
  protected $configurationManager;

  /**
   * @param Tx_Extbase_Configuration_ConfigurationManagerInterface An instance of the Configuration Manager
   * @return void
   */
  public function injectConfigurationManager(Tx_Extbase_Configuration_ConfigurationManagerInterface $configurationManager) {
    $this->configurationManager = $configurationManager;
  }

  /**
   * Set uid of the content element
   *
   * @return int $uid The uid of the content element
   */
  public function render() {
    // fallback
    $uid = uniqid();

    if ($this->templateVariableContainer->exists("contentObjectData")) {
      // this works for templates but not for partials
      $contentObjectData = $this->templateVariableContainer->get("contentObjectData");
      $uid = $contentObjectData['uid'];
    } else {
      // this should work in every circumstance
      $cObj = $this->configurationManager->getContentObject();
      $uid = $cObj->data['uid'];
    }

    return $uid;
  }
}

Still missing in core afaik. So please, do not close this.

+1 I would like it too!
(Maybe VHS has something ;))

Just a tiny update from the side lines: this issue has been reviewed, judging if it has any impact on or is affected by the merging of the standalone Fluid package as TYPO3 dependency.

Verdict: NOT AFFECTED. This feature should, however, be very carefully considered - my suggestion would be to add a ViewHelper in Fluid (the TYPO3 adapter, not the standalone package) that will return the current cObj as stored in ConfigurationManager.

Why only the uid of the content element and not all content element properties? I would need section_frame or layout…

Does anyone want this anymore? It doesn't appear to be a hot topic... ;)

From my part, I continue to think it could be useful :)

We recently needed this. Shall we implement this somehow for CMS 8?

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 10 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 11 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

Patch set 12 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46473

@Benji: AFAIK we still lack the page information in a FLUIDTEMPLATE.