Just installed and fired up the Android app, but after filling the setting and saving nothing happens.
If I add wrong user details it will tell, but if it's right it's stuck.
If I close it and reopen, settings are gone.
Btw! Is it possible to translate those apps?
If I add wrong user details it will tell, but if it's right it's stuck.
If I close it and reopen, settings are gone.
Btw! Is it possible to translate those apps?
Share this post:
Accepted Answer
On thing quite a few does, is not paying attention to the texts on the screen.
Some write full admin url, including http/https, when it should be only store url without http/https and admin.
Anyhow the one in the link from Denis (the one I was testing) wasn't available a month ago, it was released this week.
By the way, my problem connecting was this one: https://github.com/arastta/arastta/issues/573
Had debug display active at the test site.
Some write full admin url, including http/https, when it should be only store url without http/https and admin.
Anyhow the one in the link from Denis (the one I was testing) wasn't available a month ago, it was released this week.
By the way, my problem connecting was this one: https://github.com/arastta/arastta/issues/573
Had debug display active at the test site.
Responses (36)
-
Accepted Answer
-
Accepted Answer
Since it's standing just Username, and not API Username, I assume it's the regular username that should be use.
Anyhow, didn't find any docs or descriptions. The dedicated page is quite empty too: https://arastta.org/mobile -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Issue created: https://github.com/arastta/android/issues/1
No, there is no restriction for credentials usage. -
Accepted Answer
-
Accepted Answer
Problem right now is that after I restarted the demo site, I noticed there are 4 instances of the module. 3 are disabled and 1 enabled.
Trying to open and edit them, most keep coming up as permission denied. Even though I have granted permission in the administrator group. I deleted the disabled ones, and tried again and no access. I deleted all of the and installed the 1.0.0 version from the marketplace, and I can edit it, but it won't enable after saving. I think that was my problem and question before. How do you enable it if it refuses to enable. -
Accepted Answer
So this is kind of weird. I cleared the cache, and now 3 mobile assistants appear again.
Mobile Assistant - CsShop - 1.0.0 - disabled - permission denied
Mobile Assistant - Arastta - 1.0.0 - enabled - permission denied
Mobile Assistant - Arastta - 1.0.0 - disabled - accessible - won't enable
Not sure what to do at this point. -
Accepted Answer
There is no module for this one Breck, you are confusing this withe other third party version. This tread is not about the Mobile Assistant from eMagicOne.
If you are going to use the latest Mobile App from Arastta linked to by Denis, which this tread is about, you can just remove those instances - or do a new demo site if you have messed up the old one. Else it would be better to start a new tread about Mobile Assistant from eMagicOne, or even better, contact the eMagicOne support. -
Accepted Answer
-
Accepted Answer
Rune Rasmussen wrote:
On thing quite a few does, is not paying attention to the texts on the screen.
Some write full admin url, including http/https, when it should be only store url without http/https and admin.
So ... domain.com or www.domain.com ... -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Don't just assume please, but check it, a make yourself familiar with the settings in the store: https://arastta.org/docs/user-manual/system/settings/server -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
OK, I see. We're going of topic now, but I really recommend you reconsider that plan then, because of security.
Avoid having different installations available from the same root if possible, if one is hacked, all could be hacked - and you don't want a store with customer data to be hacked. This also applies to test sites, especially those being forgotten and not updated.
Make a own webroot for each site (e.g. public_html is for main, public_html_test_yourdomain or similar for subdomain etc). If your hosting doesn't support it, move on (cPanel setups does).
Btw! You also need to move and adjust your robot.txt files to root, as they are not read from subfolders, if you continue using this setup. See the included robots.txt.dist, or/and Google it. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Finally, Arastta mobile apps are looking for your valuable translations https://crowdin.com/project/arastta-mobile-apps -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »