Home Forums Plugins Store Exporter Deluxe [Resolved] Possible bug saving utf8 BOM

This topic contains 2 replies, has 2 voices, and was last updated by  Michael Visser 2 years, 5 months ago.

Welcome to our community support forums! We're here to help - but if you have an urgent request for a Pro Plugin, you will get a prioritised response through our Premium Support page.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #45951

    Dima
    Participant

    Hello Michael, I’ve done some heavy customization to SED so I looked “under the hood” so to speak))
    So I found that choosing “bom” in settings updates correctly the $export->bom, but its not written because “export-csv.php” is missing those:

            /**
             * Get whether BOM should be used
             *
             * @return boolean
             */
            public function getUseBOM() {
                return $this->_useBOM;
            }
    
            /**
             * Set whether BOM should be used
             *
             * @param	boolean	$pValue		Use UTF-8 byte-order mark? Defaults to false
             * @return PHPExcel_Writer_SED_CSV
             */
            public function setUseBOM($pValue = false) {
                $this->_useBOM = $pValue;
                return $this;
            }

    Also in many place in exporter-deluxe.php it setting this $objWriter->setUseBOM( true ); without testing the $export->bom variable.

    Thought you should know.

    #45953

    Michael Visser
    Keymaster

    Hi actv-tec, thanks for raising this. I’ll check this out with a fresh head and respond in detail. The custom CSV writer PHPExcel_Writer_SED_CSV exists within /includes/export-csv.php just to clarify for other readers.

    #45966

    Michael Visser
    Keymaster

    Hi actv-tec, busted both of those issues. I’ll get that included in the 2.2.3 release which will confirm WooCommerce 3.0 compatibility. Feel free to ping me on Support if you want an early release to look at 🙂

Viewing 3 posts - 1 through 3 (of 3 total)

The topic ‘[Resolved] Possible bug saving utf8 BOM’ is closed to new replies.