I've contacted the support staff from uberthemes, but they've been very little help & I'm seeing this issue all over the place with the latest iteration of their product.

I've got some logging running & I'm getting an error that is showing a problem with this section of code.

The error from the stack trace is "Uninitialized string offset: 0"

could someone point me in the right direction for troubleshooting this issue? I'm getting nowhere fast.

     * Sets the relative URL for the application entry script.
     * This setter is provided in case the entry script URL cannot be determined
     * on certain Web servers.
     * @param string $value the relative URL for the application entry script.
    public function setScriptUrl($value)

     * Returns the path info of the currently requested URL.
     * This refers to the part that is after the entry script and before the question mark.
     * The starting and ending slashes are stripped off.
     * @return string part of the request URL that is after the entry script and before the question mark.
     * Note, the returned pathinfo is decoded starting from 1.1.4.
     * Prior to 1.1.4, whether it is decoded or not depends on the server configuration
     * (in most cases it is not decoded).
     * @throws CException if the request URI cannot be determined due to improper server configuration
    public function getPathInfo()



            elseif($baseUrl==='' || strpos($pathInfo,$baseUrl)===0)
                throw new CException(Yii::t('yii','CHttpRequest is unable to determine the path info of the request.'));

            if(($posEnd=strlen($pathInfo)-1)>0 && $pathInfo[$posEnd]==='/')

        return $this->_pathInfo;

  • Which extension version you used to migration of data? Oct 22, 2016 at 6:20
  • 3.0.2 - it's the newest version from ubertheme Oct 24, 2016 at 12:20

1 Answer 1


Our team has resolved a similar case that was caused by wrong files/folder permission.

Beside the file/foder permission, if you use Nginx server, the issue might associate with the additional configuration for Nginx (required for our migration tool to work properly) as well.

If the case above does not refer to your ticket on Ubertheme, please submit a new ticket or let us know your old ticket url here, so that we can check and help you out.

Regards, Ubertheme team

  • ubertheme.com/question/404s-with-m2-1-2-ub-3-0-1 it gives 404 Not Found Oct 25, 2016 at 9:31
  • The ticket you mentioned was resolved today, yet the ticket's owner marked the ticket as private though. As indicated in our reply above, the folder permission might be one of the reason for either 404 or 403 issues.
    – Ubertheme
    Oct 25, 2016 at 13:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.