View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000641 | OXID eShop (all versions) | 1.04. Content, static (register, contact etc.) pages | public | 2009-02-26 12:08 | 2009-03-02 15:51 |
| Reporter | tjungcl | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.0.1.0 revision 15990 | ||||
| Fixed in Version | 4.1.0 revision 17976 | ||||
| Summary | 0000641: User-defined meta-keywords and -description not shown on start-page | ||||
| Description | There are fields for metakeywords and description in the cms-start-page(oxstartwelcome). Additionally there are two cms-pages that look like they are supposed to hold meta data for the start-page: oxstartmetakeywords and oxstartmetadescription When the oxstartwelcome-cms is called directly (www.domain.com/start-tpl-welcome-text/) it uses the meta data found directly in oxstartwelcome. But when i open the start.tpl (www.domain.com/home) there is no meta-keyword/description at all. Neither from oxstartwelcome nor from oxstartmetakeywords. | ||||
| Additional Information | I using a reduced start.tpl which doesnt show any actions, news, top-sellers or any products at all. It just shows the categories, language-switches and the html defined in the oxstartwelcome-cms-entry | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
|
|
Reminder sent to: tjungcl Hi, oxstartwelcome-cms - is used only for displaying "Welcome..." text in the Main page. This is not related to meta keywords. Meta description and keywords, as you said, are holding in oxstartmetakeywords and oxstartmetadescription cms. And for us it loads meta details correctly (cannot reproduce the case). Could you please send us this reduced start.tpl for testing localy? Best regards, Dainius Bigelis |
|
|
I's a bit complicated... i am preparing a pre-release alpha-like version of our new oxid-shop at the moment, which will in a first step be used to display our products (to users and crawlers) and will not contain any prices or a basket. For that purpose i do quite heavy reductions to your templates (not the originals, i'm using copies with names *_forwarder.tpl). Additionally in the administration nearly all performance-options are set to a minimum. The eshop only has to display categories and articles with titles, pictures, longdescs and their variants (plus cross-selling links). I was quite carefull with what i delete and tried to switch things off in admin instead of cutting them from the tpls. The modified TPLs also include tweaks to the stylesheet that could not be done with the Look&Feel tool. That will be tidied up in the future, but for now it works quite fine. I'll upload the four templates that are used in my start-page (header,left,start,footer). Edit: to use the start_forwarder.tpl i modified the views/start.php to access start_forwarder.tpl instead of start.tpl |
|
|
tjungcl: i strictly recommend not to modify sourcecode if you still wish easily update shop. I recommend you to write a module, even if it does small changes of original code. Thus your life will be much more easier :) |
|
|
I know, shame on me :( I already wrote a handfull of modules for oxid ce and these are the only 10 bytes i changed in a original php, i promise. As I requested elsewhere - it would be great if the filenames of core-templates could by defined in the administration or the config-file. Or do you mean changes in the templates? If so, i could use a documentation how to extend tpl files with modules... |
|
|
i meant this: class tjungcl_start extends start_parent { /** * Current class template name. * @var string */ protected $_sThisTemplate = 'start_forwarder.tpl'; } + module setup in admin ;) |
|
|
Shop themes can be used instead of renaming all templates. (default) out/basic/* (custom) out/forwarder/* theme can be changed in config.inc.php file: $this->sTheme = 'basic'; |
