You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install to a particular filepath immediately after composer issue && ln -s add to the documentation
add datatables parameter loadBootstrap
(automatically in load or use seek for install path or locate for a public cdn)
similar solution independently is in Yii 2 assets publification
though, doing it ourselves, finding that the SCRIPT_FILENAME must be obviously above the document root, document root might be though much more below, here url path might be similar to script filename part, though not completely as it might include also the artificial part of the url, so it will be better to rely on SCRIPT_FILENAME to obtain the canonical relative part of the path, to reflect assets correctly to th running script regardless to where is document root configured to be
other defining constraints
the document root is an absolute system filepath
SERVER_SCRIPT as as far I know also the full system filepath so the common part of the path may be removed, as the server script must reside inside the document root, therefore the remaining will reflect the correct relative path to the assets, given the script already addresses assets correctly relatively like if being nested index.php ../css, and similarly the SCRIPT_URL should reflect the same unless htaccess pretty url is used, where it would not need to remove the absolute part of the path below the document root, as it is in it's nature inside the document root unless just perhaps some special cgi scripts aliases would be used
The text was updated successfully, but these errors were encountered:
install to a particular filepath immediately after composer issue && ln -s add to the documentation
add datatables parameter loadBootstrap
(automatically in load or use seek for install path or locate for a public cdn)
similar solution independently is in Yii 2 assets publification
though, doing it ourselves, finding that the SCRIPT_FILENAME must be obviously above the document root, document root might be though much more below, here url path might be similar to script filename part, though not completely as it might include also the artificial part of the url, so it will be better to rely on SCRIPT_FILENAME to obtain the canonical relative part of the path, to reflect assets correctly to th running script regardless to where is document root configured to be
other defining constraints
The text was updated successfully, but these errors were encountered: