Jump to content

No sign in/registration in front office


Recommended Posts

I have updated from 1.4.4.1 to 1.6.0.8 on a test wamp server and there is no login or registration option in the front office for customers.  I have not been able to find anything for this.  Where can I get the native module for this?

Link to comment
Share on other sites

Yes, it is enabled, updated, cache cleared.  In live edit I can see the user info block there where it is supposed to include the sign in feature, but the sign in is just not there. I also created a separate data base and clean new install of 1.6.0.8 to try to compare it with my backup using inspect element  (though I have limited experience in using this) and it shows in the fresh install with the difference shown here from comparing the inspect element: (btw- there is no difference between browsers with this problem.)

 

backup copy: 

<script type="text/javascript">/* <![CDATA[ */;modules_list.push('blockuserinfo');/* ]]> */</script>

<div id="hook_14_module_22_moduleName_blockuserinfo" class="dndModule" style="border: 1px dotted red;height:50px;"> <span style="font-family: Georgia;font-size:13px;font-style:italic;"> <img style="padding-right:5px;" src="/public_html/modules/blockuserinfo/logo.gif">User info block<span style="float:right"> <a href="http://127.0.0.1/public_html/index.php?live_edit=1&ad=admin12&liveToken=f4ee20a142c5374df43fe385b111af22&id_employee=1&id_shop=1&live_edit&liveToken=f4ee20a142c5374df43fe385b111af22&ad=admin12&id_shop=1&id_employee=1#" id="14_22" class="moveModule"> <img src="/public_html/img/admin/arrow_out.png"></a> <a href="http://127.0.0.1/public_html/index.php?live_edit=1&ad=admin12&liveToken=f4ee20a142c5374df43fe385b111af22&id_employee=1&id_shop=1&live_edit&liveToken=f4ee20a142c5374df43fe385b111af22&ad=admin12&id_shop=1&id_employee=1#" id="14_22" class="unregisterHook"> <img src="/public_html/img/admin/delete.gif"></a></span> </span></div>

 

Fresh install:

<script type="text/javascript"> modules_list.push('blockuserinfo');</script>

<div id="hook_95_module_28_moduleName_blockuserinfo" class="dndModule" style="border: 1px dotted red;">
<span style="font-family: Georgia;font-size:13px;font-style:italic;">
<img style="padding-right:5px;" src="/prestashop_1.6.0.8/prestashop/modules/blockuserinfo/logo.gif">User info block<span style="float:right">
<img src="/prestashop_1.6.0.8/prestashop/img/admin/arrow_out.png"></a>
<img src="/prestashop_1.6.0.8/prestashop/img/admin/delete.gif"></a></span>
</span><!-- Block user information module NAV  -->
<div class="header_user_info">
Sign in
</a>
</div>
 
 
<!-- /Block usmodule NAV -->
</div>
 
In the block my account folders config xml file of the 2 databases the only difference is that one shows the blockmyaccount version as 1.3.1 and the other (fresh install) as 1.3, even though both are updated.  Don't know if that will influence things or not.
 
Thanks for your response any help you can give.
 
I guess a question from this is: could it be as simple as replacing the blockmyaccount or the blockuserinfo in my backup with a copy from the fresh install...of is there other code in other areas that need to be changed as well?
Link to comment
Share on other sites

Update:

 

I opened all the files in the 2 databases folders for the my account and user info blocks to look at the code and found no other difference except the ".1" difference in the fresh install of the config xml file noted in my last post.

 

Currently I am looking at the titles of the positions of the modules in the 2 databases to compare.  So far I have noticed that in the fresh install all the modules listed in the positions area are listed starting with either the words "action" or "display", while in the updated database there is one that start's with "dashboard" and 3 others listed just as their respective titles "facebooklike", "Googleplusone" and "myaccountblock".  I don't know if these are listed in incorrect formatting or not but I don't see a way to change them to match the fresh install database either.

Link to comment
Share on other sites

In doing some comparative analysis to try to track down what might be causing my problem...

 

Here's a bit of update vs fresh install analysis that's quite interesting:

 

- A fresh install has 2.5 times the positioning hooks (250% more) available positioning hooks compared to an update: tons more built in options for a fresh install???

- 25% of hooks that are included/exist in an update but do not exist at all in a fresh install.  Don't how much they are needed or have been replaced, etc.  But they are missing from the fresh install list.  So 75% of the hooks from an update also exist with a fresh install.

- So, comparing only the existing hooks on both, there are nearly 300% additional hooks on a fresh install more than what an update gives.

- So, unintentionally or not, are longer existing faithful prestashop customers (business owners who have been using prestashop) getting shorted nearly 300% in hook options compared to new customers who are doing a fresh install?  I was under the assumption that when we do an update, we are updating the shop to be the equivalent of a new fresh install of the newer version of prestashop.  Is perhaps this part of the reason updates have so many bugs and the cause of so much apprehension of owners to update their shops.  Done get me wrong, I do love many of the features of prestashop (when they work) and I appreciate the help given by moderators and others on the forum....but ummm....what's up with the short we get with updating?

 

Could hook mess up be a contributor to the problem I am having with my shop?

Link to comment
Share on other sites

×
×
  • Create New...