i've tried to find an answer to this question google-ing, and i was only able to find one answer that suited but, unfortunately, the patch suggested didn't work. That's why i'm placing this question here.
i'm using X2 engine v4.3 and i've recently discovered that a user (any user created by admin) is not able to view the contact information.
He/she's able to edit it, but when an opening attempt is made, the result is:
Send Error Report
Here's a quick list of what will be included in the report:
Error Code: 404
Error Message: Unable to resolve the request "contacts/id/index".
Stack Trace: [click to toggle display]
0 /var/www/vhosts/URL/framework/web/CWebApplication.php(141): CWebApplication->runController('contacts/id/ind...')
1 /var/www/vhosts/URL/framework/base/CApplication.php(180): CWebApplication->processRequest()
2 /var/www/vhosts/URL/index.php(55): CApplication->run()
3 {main}
X2Engine Version: 4.3
PHP Version: 5.4.33
The administrator user is able to see and modify contacts with no problem.
The strange part is that in localhost this error doesn't happen, the user is able to see the information, this error is happening in the web server.
Does someone has any ideia on how to fix this?
any help would be highly appreciatted.
thank you,
Related
Cross post from https://github.com/getgrav/grav/issues/3523
(don't kill me, I didn't know that it's frowned upon)
I am not sure if this is the place to ask for help, so tell me if it's not (and maybe where to ask).
I am trying to update to the latest Grav release 1.7.29 from (originally 1.6.24, while troubleshooting today updated to) 1.6.31 (using direct-install.
I tried updating with self-upgrade and direct-install <latestVersionURL>.
But, while trying to install, it gives me the following error:
Installing upgrade... [30-Jan-2022 17:04:37 Europe/Cityxy] PHP Fatal
error: Uncaught Error: Call to undefined method
Grav\Common\Utils::basename() in
/var/www/virtual/name/html/tmp/Grav-61f6b713f0bb9/zip/grav-update/system/src/Grav/Installer/VersionUpdate.php:29
Stack trace:
#0 /var/www/virtual/name/html/tmp/Grav-61f6b713f0bb9/zip/grav-update/system/src/Grav/Installer/VersionUpdater.php(126):
Grav\Installer\VersionUpdate->__construct('/var/www/virtua...',
Object(Grav\Installer\VersionUpdater))
#1 /var/www/virtual/name/html/tmp/Grav-61f6b713f0bb9/zip/grav-update/system/src/Grav/Installer/VersionUpdater.php(38):
Grav\Installer\VersionUpdater->loadUpdates()
#2 /var/www/virtual/name/html/tmp/Grav-61f6b713f0bb9/zip/grav-update/system/src/Grav/Installer/Install.php(239):
Grav\Installer\VersionUpdater->__construct('core/grav',
'/var/www/virtua...', '1.7.29', Object(Grav\Installer\Versions))
#3 /var/www/virtual/name/html/tmp/Grav-61f6b713f0bb9/zip/grav-update/system/src/Grav/Installer/Install.php(184):
Grav\Installer\Install->prepare()
#4 /var/www/virtual/name/html/system/src/Gra in /var/www/virtual/eduref/html/tmp/Grav-61f6b713f0bb9/zip/grav-update/system/src/Grav/Installer/VersionUpdate.php
on line 29
From my understanding the files between versions have been changed, and looking at the Grav documentation, the called method basenames() is now in Grav/Common/URI, not in Grav/Common/Utils.
So I assume I located the problem, but have no idea on fixing it. Since I am not very well versed on this whole topic of managing websites (never set up the site, only maintaining it), I would really appreciate a safe answer on how to update Grav to the newest version which doesn't risk me destroying the functioning of the website.
Thank you for helping! :)
Tried with:
PHP: 7.3 & 7.4
Grav: 1.6.24 & 1.6.31
Admin: 1.9.10
Host: Uberspace
via SSH
Particular issue fixed:
https://github.com/getgrav/grav/issues/3523
following issue open:
https://github.com/getgrav/grav/issues/3532
I am currently working on integrating a MapProxy WMS into my Mapbender applications.
Adding the MapProxy as a datasource works fine. Mapbender recognizes all layers and metadata.
Additionaly I can add the MapProxy WMS to an application, but when I start that application, I get the following error message on the top right:
Additionally this error "deactivates" the "wms-layer-tree" on the left (the menu where the user can activate or deactivate wms sources"
In the MapBender log, I can see the following:
[2021-02-02 14:17:22] request.INFO: Matched route "mapbender_manager_repository_view". {"route_parameters":{"_controller":"Mapbender\\ManagerBundle\\Controller\\RepositoryController::viewAction","sourceId":"225","_route":"mapbender_manager_repository_view"},"request_uri":"https://geoportal2.intra.swrag.de/mapbender/manager/repository/source/225"} []
[2021-02-02 14:17:22] request.ERROR: Uncaught PHP Exception Symfony\Component\HttpKernel\Exception\NotFoundHttpException: "Not Found" at /var/www/mapbender/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php line 251 {"exception":"[object] (Symfony\\Component\\HttpKernel\\Exception\\NotFoundHttpException(code: 0): Not Found at /var/www/mapbender/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Controller/Controller.php:251)"} []
I guess that's the Error for my MapProxy WMS because of the timestamp and because of the "sourceID":"225", which is the ID of my MapProxy WMS.
Also, if I used my WMS in a QGIS project it works fine.
Feel free to ask, if I missed explaining something. Any help is appreciated. Stay safe!
Okay.. I found the solution.
While testing the MapProxy WMS I wanted to disable it by default when starting the application.
Sadly I chose the wrong option, which let to crashing the WMS-Layer-Tree.
So if you have the same problem: don't deactivate the first option!
Today I started to get this error upon adding new events to calendar:
Fatal error: Uncaught exception 'apiServiceException' with message
'Error calling POST https://www.googleapis.com/calendar/v3/
calendars/[cal-id]#group.calendar.google.com/events?alt=json&key=[dev-key]:
(403) Access Not Configured' in /[...]/src/io/apiREST.php:86
Stack trace: #0 /[...]/src/io/apiREST.php(56): apiREST::decodeHttpResponse(Object(apiHttpRequest))
#1 /[...]/src/service/apiServiceResource.php(148): apiREST::execute(Object(apiServiceRequest)) #2 /[...]/src/contrib/apiCalendarService.php(472):
apiServiceResource->__call('insert', Array) #3 /[...]/index.php(160): EventsServiceResource->insert('[cal-id-part]...',
Object(Ev in /[...]/src/io/apiREST.php on line 86
It worked perfectly till now and I didn't change anything in code.
I had a similar problem accessing Google Analytics data with PHP. I fixed it by making sure the Analytics service was turned on for my project in my API console: https://code.google.com/apis/console/.
You may have to turn on the calendar service. See the link below for further explanation when someone had an issue with the translation service:
Translation api has stopped working
Don't know if this will help someone.
I had the same error and I had tried everything. Then I removed "developer_key" from config.php and it worked. Please note I was using Service Account https://developers.google.com/accounts/docs/OAuth2ServiceAccount
Well, they released new version and that what apparently caused errors. Got the newest version now and it works great once again.
Don't know if this will help someone, either.
It may also help to go to the respective calendar-settings page in your Google Account, edit something trivial and explicitly save again, (or re-save once more to set back to the old settings). Sometimes the google servers are a bit hesitant to accept any new settings, especially the "Sharing " settings. Check which of your service accounts have permission levels "can edit" , or "is owner" .
I am working on a GIS based application. I am using the following tools:
MapGuide Open Source 2.2
MapGuide Maestro 3.5.0.6071
Oracle 10g
Oracle SQL Developer 3.0.04
PHP 5
In MapGuide Meastro, Whenever I add a new SHP Provider feature resource and preview it in the browser, it gives the following message:
Failed to retrieve message for "MgIndexOutOfRangeException". The value is invalid because it is too large.
However, when I add an Oracle Provider feature resource, and preview it in browser, it works fine.
Googling the error message with the above configuration gives ALMOST 0 useful results. I have posted the same question even the support site, osgeo.org, long ago, but have not received a reply yet.
Does anyone working on these technologies have any idea?
EDIT
At least, I have found the root of the problem. It is in
C:\Program Files\OSGeo\MapGuide\Web\www\schemareport\displayschema.php
on line: 61
$firstClass = substr(strrchr($classCollection->GetItem(0), ":"), 1);
I resolved the issue by downgrading the MapGuide Maestro from 3.5.0.6071 to 2.1.1.5078. The interface is not as user-friendly as the latter version, but it resolved not only the problem in question, but some other problems with database connectivity also.
One more drawback, it has no support for composite geometry shapes.
Thanks
When I installed the Magento program on my local environment, after finishing the install, I accessed the URL http://localhost/job/magento/ and it shows the following error.
There has been an error processing your request
Illegal scheme supplied, only alphanumeric characters are permitted
Trace:
#0 D:\www\job\magento\app\code\core\Mage\Core\Model\Store.php(712): Zend_Uri::factory('{{base_url}}')
#1 D:\www\job\magento\app\code\core\Mage\Core\Controller\Varien\Front.php(313): Mage_Core_Model_Store->isCurrentlySecure()
#2 D:\www\job\magento\app\code\core\Mage\Core\Controller\Varien\Front.php(161): Mage_Core_Controller_Varien_Front->_checkBaseUrl(Object(Mage_Core_Controller_Request_Http))
#3 D:\www\job\magento\app\code\core\Mage\Core\Model\App.php(349): Mage_Core_Controller_Varien_Front->dispatch()
#4 D:\www\job\magento\app\Mage.php(640): Mage_Core_Model_App->run(Array)
#5 D:\www\job\magento\index.php(80): Mage::run('', 'store')
#6 {ma
How to correct it? Thank you!
Please install magento with localhost Ip Address 127.0.0.1
Ex: http://127.0.0.1/job/magento/
Try loading https://localhost/magento.
Note the https instead of http.
Solved this problem by checking the third checkbox ("Skip Base URL validation before next step") in the first screen after the agreement.
I installed under a FQD on a LAMP server.
I fixed this problem changing the directory permission to 755, as it's said on installation guide
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/magento_installation_guide
Solved this problem by checking the third checkbox ("Skip Base URL validation before next step") in the first screen after the agreement.
and using firefox
when i use chrome , i meet issue after installing.
i don't know why
Try this it will definitely helps you... https://127.0.0.1/magento/
You can try to change base_url variable directly from the database.
Use phpmyadmin or any other software to go to your magento database.
In "core_config_data" table find entry for web/unsecure/base_url and change it to either "{{base_url}}" or http://127.0.0.1
Do the same for web/secure/base_url
Have same problem on Wamp and XAMPP., nearly give up.
Finally find the solution, Magento 1.6 can not work properly with WAMP 2.1 and XMAPP 1.7, I guess it caused by Mysql version, not sure.
but after I change WAMP to 2.0 i, everything is fine. Magento 1.6 is running well.
Download WAMP2.0i : http://sourceforge.net/projects/wampserver/files/WampServer%202/WampServer%202.0/WampServer2.0i.exe/download
I failed to install on Chrome, but success on firefox.
Good Luck.
This usually happens to me when I install magento sample data after installing magneto, you should do it other way around (same data wipes out core_config_data table).
from http://www.magentocommerce.com/download:
sample data - Must be installed prior to the basic Magento Installation.
When you install 'configure' step of magento installation, you MUST use 'http://127.0.0.1/magento/' at base url textbox, instead of 'http://localhost/magento' do this.
Good Luck.
There has been an error processing your request SQLSTATE[28000] [1045] Access denied for user \\\’demo\\\’#\\\’localhost\\\’ (using password: YES)
This error will occur if there is no database connection .. First you need to check your local.xml file ... then check the url path in core_config_data in your database .... clear your cache session and locks .... if the error still appear after doing all these things \\"YOU JUST LOOK IN YOUR app/etc folder ...... if there is any extra xml file just delete that particular file ...... i got the same issue .. found a local_org.xml file in etc folder ....... JUST DELETE THAT FILE IT WILL WORK PROPERLY .......... grin