I am running Developer Edition, Fluid Style 2 template. I just installed the seller store and got this error when trying to input a description, title and picture. Any thoughts? Fatal error: Call to undefined method Format::inputSQL() in /home/kengland/public_html/modules/seller_store/index.php on line 141 And also I have included in my showlisting templates the featured listing plugin. I would like to not include this plug in if someone has a seller store. Would this work? {if $storeTitle<>"" || $storeDescription<>"" || $storeImage<>""} {else} <h2>{$smarty.const.LANG_FEATURED_LISTINGS}</h2> {css_listings_horizontal number=4 type="featured"} <br/> {/if} Just found that if I enter through administration it works and shows when i log in and check my store through my site. Thank You
Just checked the database and when inputing title, picture and description through administration it is in there but when clicking view more ads from this seller the store does not come up. I am using custom categories and the showlisting files do include the seller store. Also the default showlisting in Fluid 2 includes the seller store.
Does it work if you use the default template showlistings file instead (simply rename the showlisting.tpl file you are using in the fluid-2 template temporarily so it is not going to get used).
I have renamed and also tried deleting the showlistings.tpl file from fluid 2 folder and somehow it still uses this file. I am using the featured listing plugin on this file which is not in the default file. Even though I have deleted this file from fluid 2 it still comes up with the featured listings which means somehow it is still using this showlistings file from fluid 2. I have even deleted cookies. I can't get it to use the default showlistings file. Is this possible?
Try emptying your browser cache and the contents of your templates_c folder. Seems like you are messed up somewhere. If the file has been renamed it cannot be used can it.
Yes, I just downloaded it. That did the trick, I am now using default showlisting file and still no seller store. I did notice that the template files in the templates folder seller store module are php files. Is this correct? index.tpl.php seller_store_admin.tpl.php This is how they are called for use $class_tpl->assign('body','seller_store_admin.tpl.php'); $class_tpl->assign('body','index.tpl.php');
Getting Closer I have downloaded and installed the current version 2.1.0 of the Seller Store. I can enter title, logo and description through administration and everything works fine. I have included a screenshot of the user seller store. The title and logo work fine but the text editor only parts of it work. It doesnot register headings but did store a bold tag. The layout is off and seems to be displaying description tags over everything. The store displays fine through the showlistings. I am using IE8.
Back to basics! You are correct. When I deactivated the Nustyle 2 template module and switched to purple and any of the other stock templates it worked just fine. Thank you for the insight and your patience.
You are using quite an old showlistings file in Nustyle and you will need to upgrade it by taking the code from the default showlistings.tpl file. It should then work fine.
User display issue The default showlisting.tpl is being used and does show seller store. I have renamed the nustyle 2 showlisting.tpl which utilizes the default. The issue is how the user admin is displaying and text editor works when a user clicks on the My Store link. When I log in under administration under the seller store module admin, that works and displays fine.
Difficult to understand your issue. What store link )- where - please try to explain. If you are using the default showlistings then there should be no issue. Can't see whythere would be an issue if you use another template showlistings either. Screenshots would help.
The editor is javascript and setting your site to use the default template can help troubleshoot if its a javascript conflict at the template level. This is why people always say to revert to an UNMOLESTED copy of the complete DEFAULT template. You have to remember that the mods for 68C are often created using the 68C default template so if any issues arise that should be the template you use to make sure the module is installed and working correctly. Then, if you change to your preferred template and things dont work it can help you an your template designer pin poi nt the problem. If yu are going to ignore requests from people to help you troubleshoot this issue then you are likely going to have to solve this one on your own.
Demo I am sorry, but i have done everything that was suggested, i have not been ignoring anyone.Your help and time is greatly appreciated. I have went back to stock templates and it does work fine with the stock templates as described in previous posts. I have reinstalled nustlyle 2 templates and turned my site on if you would be willing to register and click on the my store link in the main navigation. This should show you what is going on. When using the text editor, it does not function correctly. You can submit, but for example if you insert a H1 tag, it will not take. The title and store image function properly when submitted. The editor works fine if i go through 68c administration under seller store admin. The site is monroemetro.com. I do apologize for any miscommunication.
Well first of all you are not using a Nustyle template from what I can see but the Fluid style. I successfully registered, showlistings appears to be working correctly. Now the my store link is bringing up an editor but the menu bar is corrupted. The cause is not clear but it looks like something is wrong with the javascript because your template switcher is not working correctly either. What I would do is deactivate the templatecodes module and the store module. Then upload all the modules again and activate the templatecodes module first. Make sure the template switcher works activating the store module. Another thing you could try is to choose one color only and deactivate the template switcher. Then test the store module. Failing that you may need to go back and ask the developer of the store module about potential javascript conflicts.
