[FIXED] Problem with Frontend-Administration for non-Backend Users

[Mordor]

Preston Moore if you go to a product on your website and change it do you see also no buttons to save?

[Preston Moore]

I don't have any buttons to SAVE, APPLY, Etc...  I don't understand how this is called a stable release. 

Letting clients have access to the frontend admin is one of the key features.  Granted, VM is a free component, but to be called stable?

Anyway, again, no save button.  Frontend Admin = USELESS

[HarryKare]

Using Joomla 1.5.6, VM 1.1.2
Problems:
Clicking on the edit icon when viewing a product
- With Joomla SEF turned on editing works fine and toolbar shows
- With sh404sef enabled the toolbar does not show, cannot save changes, etc
Similarly with sh404sef enabled, going to the frontend admin and then clicking on any link adds back my template making it almost impossible to perform the functions and I believe toolbar is missing

I put a post at
http://extensions.siliana.com/forums/index.php?topic=10155.msg14032#msg14032
explaining research I did, a temporary workaround that works for me and asking for assistance because I am concerned what problems it might create. See that message for warnings, possible solutions and hopefully some answers. From what I see, this is not a Virtuemart problem, it is a sh404sef issue.

[Mordor]

Your right it is a SEF404 issue...
I hope they will solve this problem so that working in the frontend section is again possible.

Thanks for posting it on there form m8!!

[Preston Moore]

Here's another post for a possible solution.  I haven't tried it yet, but it until we can verify that Harry's fix doesn't affect anything else, it seems a little more "stable" of a fix.

http://extensions.siliana.com/forums/index.php?topic=9363.0

Please keep this thread going so we can figure this out!  If anyone has success with either of the two, please let us know here...

[HarryKare]

Unfortunately still no answer in here or in the bug reports on this problem, that is disappointing at best. Here are the other postings I placed on the topic

http://extensions.siliana.com/forums/index.php?topic=10155.0
http://joomlacode.org/gf/project/sh404sef/tracker/?action=TrackerItemBrowse&feedback=Successfully%20added&tracker_id=514


I tried the very advanced settings change for $shDefaultParams['sh404SEF_NON_SEF_IF_SUPERADMIN'] = 1;
and that caused additional front end admin problems as well as not showing the save or cancel if editing a product from the front end.
The change I made listing within the siliana.com site above is the only one that has worked for me so far.

Harry

[Mordor]

Harry you mean this solution?

---
I found a work around. I forced non-sef url for Administrator (I'm super admin, so I have backend login, only admin must use front end admin). This was done through the very advanced tab, and changing the one parameter in sef404.class.php in /administrator/components/com_sef from super-admin to admin.

A bit crude, but it worked. When the admin logs into the front-end , he doesn't get sef url's, so the link to shop admin works
---

I don't know what i have to do to get it working can you explain what you did to get it working?

[HarryKare]

Yes the following potential solution
"I forced non-sef url for Administrator"
Regardless of using the default super admin, admin, etc settings in very advanced configuration, I had all sorts of problems with templates, missing save buttons, etc from the front end and gave up.

The only solution that has worked so far is the one I posted, but still have heard nothing from sh404sef support or if anyone else found problems with that solution. I am moving forward with this option in live accounts since I have sites needing the sef urls and who also admin products from the front end who do not have back end access.

Harry

[Mordor]

(only admin must use front end admin). This was done through the very advanced tab.

What does this mean?
What i have to do or change?

[HarryKare]

It's from the post above
http://extensions.siliana.com/forums/index.php?topic=9363.0
Essentially you go to components->sh404sef->configuration->very advanced and you'll see a place to change a parameter to allow super admin to not have sef urls when accessing from the front end. The link also discusses changing it from only super admin to admin, in either case it caused problems for my installation and did not work. You can follow the most recent postings in this thread to see links to my postings and another potential solution.

Harry

[Mordor]

It's from the post above
http://extensions.siliana.com/forums/index.php?topic=9363.0
Essentially you go to components->sh404sef->configuration->very advanced and you'll see a place to change a parameter to allow super admin to not have sef urls when accessing from the front end. The link also discusses changing it from only super admin to admin, in either case it caused problems for my installation and did not work. You can follow the most recent postings in this thread to see links to my postings and another potential solution.
Harry

That doesnt work for me

[reders]

I have got the exact same problem, another issue with front end admin using Joomla 1.5.7 and VM 1.1.2

This is causing me no end of trouble on live jobs, if anybody finds a solution please post it in this thread.

Regards,
Reders

[HarryKare]

The code I posted in
http://extensions.siliana.com/forums/index.php?topic=10155.0
works for me. Yannick from sh404sef replied to my bug report on 10/24 saying the code I remarked out may not be needed anymore and he would look in to it, I haven't heard a final answer. Here is the bug report link again.
http://joomlacode.org/gf/project/sh404sef/tracker/?action=TrackerItemEdit&tracker_item_id=12912

[Spencerk]

Hi guys - was there a definite fix for this?  Did the above code work?

Thanks.

[HarryKare]

The code that I submitted in the following thread has worked for me without issue.
http://extensions.siliana.com/forums/index.php?topic=10155.0
I posted a support ticket in September and got the following response in October
"THis was added to workaround some relative links issues in VM 1.1, and may not be needed anymore. I'll try dig in to this as well"
I haven't heard back since.

The code is easily changed so I'd give it a try.

Harry