May 12, 2015 at 11:21 pm 43794
After I chose this permalink settings (as shown here http://postimg.org/image/fnla5lz0v/) and created .htaccess file in dokan directory, I could NOT log in anymore. Whole site gone into disastrous when no user could have logged in. Whenever user clicked the login page, it will return "HTTP 404 NOT Found"
Below is the .htaccess file
May 13, 2015 at 10:49 am 43826
Please provide your login and ftp details by using this form: http://wedevs.com/provide-login-details/. I will have a look what is going wrong.
Thank you 🙂
May 13, 2015 at 2:13 pm 43851
I had submitted the login info.
May 13, 2015 at 2:57 pm 43859
I also need your ftp details.
May 18, 2015 at 2:04 pm 44337
|Atilla||This reply has been marked as private.|
May 18, 2015 at 2:32 pm 44342
I will inform you after finishing our work. Please keep patience.
May 20, 2015 at 4:40 pm 44645
Your ftp is not working. Please provide us correct details.
May 20, 2015 at 5:58 pm 44662
resubmitted. please check.
May 20, 2015 at 6:25 pm 44671
Thank you. After finishing my work i will inform you.
May 21, 2015 at 12:22 pm 44760
We have checked your site. You have to contact with your hosting provider. There is problem with your server user permission.
May 22, 2015 at 8:49 am 44867
I managing my own server.
Common corporate practice is that root privilege shall NEVER be granted to vendors. This is good for both sides having to deal with potential liabilities, and passing technical audit. Though without the write permissions, I’m expecting if vendor could see what files had been set incorrectly, and please advise me how to correct it, if any.
Kindly advise soonest.
PS. The more users knew how to use the product, the less they will bother vendors, which is a win/win. So please teach me how to fix the issues. Thank you
May 23, 2015 at 11:59 am 44921
May 23, 2015 at 1:04 pm 44927
Thank you for your suggestion. Your suggestion will help us to make more strong documentation. Permalinks setting work perfectly for every user. For product it is common setting. But your issue is not with our plugin or any functionality.