typo3-coreapi / ext-coreapi Goto Github PK

Purge deleted records older then X days/weeks/months

Because we use corapi for deployment over TYPO3.Surf, a update for the languagefiles from repository would be a nice feature!
At this time we had to do the update manually.

Thx!

• Throw an exception when the action is missing
• Use constants instead of integer values

currently some code is duplicated in the Dispatcher.php and the extbase-driven CommandControllers.
I really like to get rid of the Dispatcher.php thing as soon as 4.5 is not supported anymore and encourage people to use the CommandControllers (available from 4.7+)

So if using the Dispatcher in >=4.7 should output a warning and log in the deprecation log.

The ext_autoload.php file seems to be missing some classes:

• 'tx_coreapi_cli_dispatcher' => $extensionClassesPath . 'Cli/Dispatcher.php',
• 'tx_coreapi_command_extensionapicommandcontroller' => $extensionClassesPath . 'Command/ExtensionApiCommandController.php',
• 'tx_coreapi_service_siteapiservice' => $extensionClassesPath . 'Service/SiteApiService.php',

Make this extension available for everyone via TER :)

,,,,,
q°_°p
`| |´

FileApi fixPermissions

cli_dispatch.php extbase coreapi FileApi:fixPermissions www-data www-data
cli_dispatch.php extbase coreapi FileApi:fixPermissions www-data www-data {fileadmin:'ug+rw',typo3_src:'g+rx'
Frage: welche rechte werden wo benötigt, welche api ist angenehm

In 6.2 the composer.json crashes the backend tool on dependency check.
#1382276561: The package "coreapi" depends on "lw/typo3cms-installers" which is not present in the system.

This is caused due to the unknown lw/typo3cms-installers. Why don't you use composer core installers?

You can than manually locate it where you want.

"require": {
"composer/installers": "~1.0"
},

with
"type": "typo3-cms-extension",

See https://github.com/composer/installers

If this is used, the 6.2 environment will be correctly handle the package.

from TER (optionally git)

check EXT:sysutils (backup): https://github.com/NamelessCoder/sysutils

Something like the TypoScript ObjectBrowser

Parameters:

• setup/constants
• (optional) specific page id
• (optional) TypoScript path (to filter sub object trees) "plugin.tx_foobar"

t3lib_tcemain->clear_cacheCmd('temp_cached') will not work with TYPO3 <= 4.7, because you need to be admin to do that:

case 'temp_CACHED': if ($this->admin && $TYPO3_CONF_VARS['EXT']['extCache']) { $this->removeCacheFiles(); }

It seems this restriction was removed in 6.0

The arguments for database:databaseCompare only documented in the code :)

const ACTION_UPDATE_CLEAR_TABLE = 1;
const ACTION_UPDATE_ADD = 2;
const ACTION_UPDATE_CHANGE = 3;
const ACTION_UPDATE_CREATE_TABLE = 4;
const ACTION_REMOVE_CHANGE = 5;
const ACTION_REMOVE_DROP = 6;
const ACTION_REMOVE_CHANGE_TABLE = 7;
const ACTION_REMOVE_DROP_TABLE = 8;

Would be fine, if the arguments documented in the inline-help or/and in documentation.

Thanks for your great work!

Suggested by madsbrunn in #18

While we are at it I suggest normalizing the signature for the coreapi < 4.7 dispatcher and the extbase command controllers.

Right now we have:

./cli_dispatch_phpsh coreapi site:info
and
./cli_dispatch_phpsh extbase siteapi:info

??
Why not use

./cli_dispatch_phpsh coreapi site:info
./cli_dispatch_phpsh extbase site:info

or

./cli_dispatch_phpsh coreapi siteapi:info
./cli_dispatch_phpsh extbase siteapi:info

run/check the reports from the reports module

Hi @Konafets, composer dependency to vfs breaks install via EM. Seems to be WIP. Cheers

Print the TS-template (on CLI). What would the syntax look like for this command?

PHP Fatal error: Call to a member function decodeExchangeData() on a non-object in .../typo345/htdocs/typo3conf/ext/coreapi/Classes/Service/ExtensionApiService.php on line 509

$fetchData = $this->terConnection->decodeExchangeData($fileContent);

The initialization is missing...

Is there any way of print all available commands from the command line? Or do you need to have TYPO3 4.7+ for that?

• Class/Method documentation
• Update the copyrights to 2013 and check GPL header
• CGL

Separate the dispatcher class from the instantiation and start() call so the class can be unit-tested

Add some basic unit tests

coreapi should return proper exit codes if some gone wrong (e.g. user has no rights to clear the caches)

suggested by Martin Ficzel during the T3DD13.

./typo3/cli_dispatch.phpsh coreapi
PHP Fatal error: Class 'Tx_Coreapi_Cli_Dispatcher' not found in /Sites/typo345/htdocs/typo3_src-4.5.27/t3lib/class.t3lib_div.php on line 5376

The ext_autoload.php should be regenerated or the dispatcher class should be added manually like this:

'tx_coreapi_cli_dispatcher' => $extensionClassesPath . 'Cli/Dispatcher.php',

Why should this file be automatically generated? Can we change this behaviour to care for it manually?

Print the page tree and partial trees (on CLI). What would the syntax look like for this command?

Following functions do not work with TYPO3 CMS >= 6.2

• #63 Make extensionapi:updatelist working with TYPO3 CMS >= 6.2
• #64 Make extensionapi:install working with TYPO3 CMS >= 6.2
• #65 Make extensionapi:uninstall working with TYPO3 CMS >= 6.2
• #66 Make extensionapi:configure working with TYPO3 CMS >= 6.2
• #67 Make extensionapi:fetch working with TYPO3 CMS >= 6.2