bdunogier

<?php
file_put_contents( 'progress.txt', '' );

$targetFile = fopen( 'testfile.iso', 'w' );

$ch = curl_init( 'http://ftp.free.org/mirrors/releases.ubuntu-fr.org/11.04/ubuntu-11.04-desktop-i386-fr.iso' );
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt( $ch, CURLOPT_NOPROGRESS, false );
curl_setopt( $ch, CURLOPT_PROGRESSFUNCTION, 'progressCallback' );
curl_setopt( $ch, CURLOPT_FILE, $targetFile );

bdunogier

Ibexa DXP has allowed multiple user content types for a while now, but there is no documented, native way to change the user content type used for registration based on the siteaccess.

As it turns out, it is quite easy with a bit of tweaking.

The EzSystems\EzPlatformUser\ConfigResolver\ConfigurableRegistrationContentTypeLoader service is used by the registration process to provide the user content type used for

bdunogier

<?php
class eZCachedModule
{
    public static function generate( $file, $args )
    {
        extract( $args );

        $tpl = templateInit();
        $tpl->setVariable( 'value', $Params['Value'] );

bdunogier

<?php /* #?ini charset="utf-8"?

[ClusteringSettings]
FileHandler=eZDFSFileHandler

[eZDFSClusteringSettings]
MountPointPath=/opt/nfs/ezpublish
DBBackend=eZDFSFileHandlerMySQLiBackend
DBHost=localhost
DBPort=3306

bdunogier

{
  content (id: 87) {
    fields {
      fieldDefIdentifier
      value {
        ... on TextLineFieldValue {
          value
        }
 ... on RichTextFieldValue {

bdunogier

ArticleContentConnection:
    type: relay-connection
    inherits:
        - DomainContentByIdentifierConnection
    config:
        nodeType: ArticleContent

bdunogier

<?php
/**
 * @license For full copyright and license information view LICENSE file distributed with this source code.
 */
namespace BD\SandboxBundle\Command;

use eZ\Publish\Core\MVC\Symfony\Routing\RouteReference;
use eZ\Publish\Core\MVC\Symfony\SiteAccess;
use Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand;
use Symfony\Component\Console\Input\InputInterface;

bdunogier

curl -v -X POST \
   https://localhost:8000/graphql \
   -H 'Cookie: eZSESSID21232f297a57a5a743894a0e4a801fc3=3p30i5bu4h8seeu6avubimdj4c; eZSESSID98defd6ee70dfb1dea416cecdf391f58=igsqlrp39miio4h4a1ddc7b1et' \
   -F 'operations={"query":"mutation CreateImage($name: String!, $alternativeText: String!, $file: FileUpload!) { createImage( parentLocationId: 51, input: { name: $name, image: {name: \"Son-Gohan\", alternativeText: $alternativeText, file: $file} } ) { _info { id mainLocationId } name image { fileName alternativeText uri } } }","variables":{"file": null, "name": "Gohan", "alternativeText": "Final cell battle"}}' \
   -F 'map={"0":["variables.file"]}' \
   -F "0"=@/Users/bdunogier/Documents/Capture\ d’écran\ 2019-03-07\ à\ 00.50.42.png

bdunogier

<?php
/**
* This file is a demonstration of the eZ PUblish REST API developer preview. It handles oAuth2
* authorization, and will return as-is the JSON content returned by the REST interface.
*
* It doesn't cover the whole thing, but almost, and should give you all you need to get started
* with it !
*
* It accepts a few URL parameters that just change which REST resource is used:
* - resource: the REST resource URI that should be queried: content/node/2,

bdunogier

{
  content
  {
    articles(query: { Created: { after: "yesterday" } }) 
    {
      title { text }
      body { html }
      image { 
        alternativeText
        variations(identifier: "large") { uri}