Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Olá pessoal ao tentar atualizar a seguinte mensagem de erro aparece:

    “N?o foi possível atualizar o banco de dados. Tente novamente”.

    Investigando o log do servidor encontrei a seguinte entrada no instante da execu??o:

    [10-Sep-2021 19:39:36 UTC] Erro de banco de dados do WordPress Specified key was too long; max key length is 1000 bytes para a consulta CREATE TABLE wp_pgly_pix (
    						<code>id</code> INT NOT NULL AUTO_INCREMENT,
    						<code>oid</code> INT NULL COMMENT 'Order ID',
    						<code>txid</code> VARCHAR(255) NOT NULL UNIQUE KEY,
    						<code>e2eid</code> VARCHAR(255) NULL,
    						<code>store_name</code> VARCHAR(255) NULL,
    						<code>merchant_name</code> VARCHAR(255) NULL,
    						<code>merchant_city</code> VARCHAR(255) NULL,
    						<code>key</code> VARCHAR(255) NOT NULL,
    						<code>key_type</code> VARCHAR(255) NOT NULL,
    						<code>description</code> VARCHAR(255) NULL,
    						<code>amount</code> DECIMAL(8,2) NOT NULL,
    						<code>discount</code> DECIMAL(8,2) NULL DEFAULT 0,
    						<code>bank</code> INT NULL,
    						<code>brcode</code> TEXT NULL,
    						<code>qrcode</code> TEXT NULL,
    						<code>receipt</code> TEXT NULL,
    						<code>metadata</code> TEXT NULL,
    						<code>type</code> VARCHAR(10) NOT NULL DEFAULT 'static',
    						<code>status</code> VARCHAR(10) NOT NULL DEFAULT 'created',
    						<code>expires_at</code> TIMESTAMP NULL,
    						<code>updated_at</code> TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP NOT NULL,
    						<code>created_at</code> TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,
    						PRIMARY KEY (<code>id</code>),
    						INDEX <code>oid</code> (<code>oid</code>),
    						INDEX <code>type</code> (<code>type</code>),
    						INDEX <code>status</code> (<code>status</code>),
    						INDEX <code>expires_at</code> (<code>expires_at</code>)
    					) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci feita por do_action('wp_ajax_pgly_wc_piggly_pix_upgrader'), WP_Hook->do_action, WP_Hook->apply_filters, Piggly\WooPixGateway\Core\Ajax->pgly_wc_piggly_pix_upgrader, Piggly\WooPixGateway\Upgrade\VersionUpgrader->upgrade, Piggly\WooPixGateway\Upgrade\VersionUpgrader->upgrade_database, dbDelta

    No caso meu banco de dados é do tipo MyISAM e usa collation: utf8_unicode_ci. Espero que esses dados ajudem a corrigir o problema.

    Thread Starter marcioluizdesign

    (@marcioluizdesign)

    OK.

    Thread Starter marcioluizdesign

    (@marcioluizdesign)

    OK my page contains that shortcode.

    I’ve follwed 100% equal the installation manual in here.

    Now I can complete a purchase, and then I’m redirected to pagseguro’s payment page.

    But If choose not to pay now, and later do a new login on the website and go to My Account > Pay, the Pay page loads blank.

    And the shortcode [woocommerce_pay] is in there.

    I’ve also increased the Total amount of memory for wordpress to 96M, more than sufficient.

    Thread Starter marcioluizdesign

    (@marcioluizdesign)

    Claudio, my problem is:

    the page: “https://mysite.com/checkout/pay&#8221;, opens completely blank.

    When I try to do a purchase it doesn’t send me to pagseguro’s page.

    Yes I’ve done the configuration just like in the installation tutorial.

    Thread Starter marcioluizdesign

    (@marcioluizdesign)

    Thanks for any help that can come and for the great work with this plugin!

    Thread Starter marcioluizdesign

    (@marcioluizdesign)

    The conflict was with the keyword statistics plugin.

Viewing 6 replies - 1 through 6 (of 6 total)