t3framework / t3 Goto Github PK

Hey, just reporting the issue that i have encountered today, i have been changing and customizing ja_mero 1.0.1 and have made changes to custom.css, it is not being picked up by template at all. i have changed a lot of things and not one change is reflected on the site.

Have cleared the cache etc.

• Access thememagic
• View megamenu
  --> Menu icons can not be loaded.
  

By default, this module is not right aligned when development mode is off. When compile LESS to CSS, it is fixed. Maybe some css file is missing.

• When I add a blank column, then save --> the submenus are duplicated.
  

Some tooltips of parameters in back-end does not make sense

The 1.1 release seems to break the list categories layout. I've attached two pictures, the first is with RC2 which seems to show it correctly, with evenly spaced categories and post count. In the 1.1 release the categories are note evenly spaced and the post count is missing

• IE 8: css issues
• IE 10: can not display megamenu
  (It's ok in IE 9)

From a user:

When using Theme Magic, see the Hex numbers, but not the color in the little color selector box. I discovered If I copy and re-paste the Hex in, then it shows up, but by default it is blank (no color shown)

Having image icons (i.e. in /images/icons/incon1.png) defined in menu items, they are not displayed properly in megamenu configuration, because in Backend they are resolved by /administrator/images/icons/incon1.png). Insted, just the alt-text is displayed.

What do you think about adding a badge that lets the user know if a setting is controlled across all styles or just for that style?

eg for general params there is a badge that says something like "global param", while on the theme and layout panels there is a badge that says something "style param"?

• Open Thememagic in Firefox 19.0, it shows error:

TypeError: wnd.location is undefined
[Break On This Error]

if(wnd.location.href.indexOf('themer=') == -1){

• In iPad, the icons: Email/Print of article item page does not work

Following on from our discussion on skype here is my suggestion to add the classes to the body.

My main question is whether we should make this flexible eg allow the developer or user to determine which classes to render and how we should do this.

So should we:

1. Just provide a core class that renders all possible classes for that view?
2. Or provide the ability for users to name the classes they want to render.

Which classes should we render?
$option = JRequest::getCmd('option', '');
$view = JRequest::getCmd('view', '');
$layout = JRequest::getCmd('layout', '');
$task = JRequest::getCmd('task', '');
$itemid = JRequest::getCmd('Itemid', '');
$catid = JRequest::getInt('catid');

Plus ...
home /not home
Logged in / not logged in
Language
Style name or id

Any others I've missed?

Would be useful to have a logo module option.

Where the options would be

• text
• image
• module

Module should be raw output.

• We should add function to show/hide content in responsive layouts (in the previous version, we only allow to show/hide modules)

I think it would be good for the users to be able to change the widths of the sidebar, main column and also the logo in the responsive tool.

At the moment the default 500 error page is displayed if the user installs the plugin and it isnt published.

Would be good to create a good looking error page that will give the end user a better idea about how to rectify the issue.

• Go to template manager => Click Layout tab => CLick Save as copy button ===> see error as image
  

For now you can't override core component (like com_content) in the html folder of the template.
I found a solution here
http://www.joomlart.com/forums/showthread.php?82329-Overriding-T3V3-core-Joomla-component-module-templates

but in my opinion this should be integrated in next version,
By the way 👍 thx for the great work,

Currently on module admin area on Joomla 3.0, there is tab called "Advanced Options" that is standard for all modules and the programmers does not need to add it to XML, because Joomla adds it automatically.

This is a great feature and users can change the look of their modules on the admin area, without the need to go to code, so, they can change tags, headings, chrome style, bootstrap size and more...

Anderson was the one that actually added it to Joomla 3.0, based on my ideas and he actually made a plugin for Joomla 2.5 to have same functionality.

I would suggest to incorporate the work that Anderson have done to T3 Plugin, so, J2.5 and J3.0 users can experiment and share the same experience and of course, if a template makes use of this, both version would work good

• Menu type = Single article
• Disable article title (in the menu setting)
  --> the <aside ..>... is still available
  

• When I install T3 in joomla fresh. The first time I open ThemeMagic, the modules in the panel has different colors with front-end. It should be the same.
  

• When installing Hikashop and Jomsocial extensions, all pages show errors: "TypeError: jQuery(...).chosen is not a function"
  

I'm on 1.1.0 RC2.

I have a menu with submenus, and after changing the child menu items' parents and doing some renaming, I can't get the mega menu designer to show these items anymore. When the segmented control has "submenu = yes" there simply aren't any items to work with.

I should say that it initially showed these items until I did some menu reorganization, and then stopped showing them altogether. Are there megamenu config rows I should delete for a temp solution?

Standard Joomla menu displays them fine with their child submenus.

My menu config for "Community":

Mega menu designer not showing any items for Community:

• In the Theme setting, select Logo type = Image
• Browse image to replace current logo image
• Save
  --> Logo image does not change
  

• When changing order of menu items from: Menus --> Main Menu --> Menus
• Error in front-end as image below
  
• Menus are duplicated
  

• site indicates the missing of custom.css file.
  

• In Joomla 2.5, when you select a menu item, the setting panel of the menu item is out of the setting box.
  

The show / hide function for displaying relative params seems not to be working at the moment.

I thought it was me but it seems that the optimise css dependancy for the dev mode param isnt working either.

Regardless of the setting I still see the optimise css button.

Have I missed something here?

• Enable option: "Hide when Collapse"
• on small screen like iphone, the icon that indicate a menu has sub-menu still displays.
  
• For the menu items, we have to double touch to open the menu. The first touch is to open sub-menu but when hiding sub-menu, we should consider it as a menu item that has no sub-menu.

• When T3 is not default template --> its back-end layout is broken. Some buttons like: Close does not work.
  

I noticed in the MegaMenu, the Item-ID isn't written out in CSS like in the Joomla Core Module. It be great if we could get that into the MegaMenu so it would be consistent and allow someone to target those individual menu item's via css. This class would be added in addition to the other ones present on the LI tag already.

<li class="item-ID"><a>...</a></li>

• In T3v2, we have option to add description for menu item, we could consider to support this feature in T3 framework.
  Let's check an example
  

I upgrade RC1 to RC2. Furthermore I had a mega menu with a few items containing a submenu. On these submenu's I placed several modules. After the upgrade the front-end is showing 'normal' sub menus instead of my customized menu containing modules. When trying to change the mega menu in the back-end, none of my changes are saved. After saving it keeps reverting to the previous settings.

Upgraded today via JA Ext Manager.

PHP Fatal error: Class 'T3Bot' not found in XXX/plugins/system/t3/t3.php on line 32
PHP Warning: include_once(): Failed opening 'XXX/plugins/system/t3/includes/core/bot.php' for inclusion

This broke administrator too. I cans see that the bot.php include file isn't there, or perhaps the upgrade hiccuped and didn't finish.

I'm not sure if something failed badly during the upgrade, or what. How can I manually effect the upgrade from the git project? For now I replaced the plugins/system/t3 folder with a copy of 1.1.0 RC2.

EDIT: Sorry to be 'that guy.' I thought perhaps it was a bug related to refactoring, but I upgraded in the Joomla extension manager and it worked second time around. All good.

As you are using your own version of bootstrap rather than Joomla3.0's built in version; how about breaking it up in to parts and allowing users to only include the parts they want to use when they compile.
IE if you don't have forms, remove the forms part.

I know this can be done in the less files with bootstrap master but many users might not be willing to touch the less files and could benefit from some toggles to turn some parts on and off to cut down on the stylesheet size.

I found 1 bug, there is a conflict with modal and the item view of k2 (which is using the modal capabilities of Joomla!).

The popup image is showing above the page over all the content when you open up an item.

• set to hide sub-menu
• set group option = no
  --> in front-end, icon that indicates a menu that has sub-menu still displays
  

I have 3 access levels in use on my site: Public, Guest, and Registered. Guest was an access level and user group that I defined to solve the issue of needing to show a "Signup" menu item that is mutually exclusive with the "User Menu," which shows items like Profile, Logout, etc.

I noticed that in the Mega Menu designer in T3 Template manager, the menu item visibility varied according to whether the user was logged into the front end or not. If I save the configuration for my Registered group-only menu, the configuration for the Guest group-only menu is lost.

I tried setting all my menu items to Public, the configuring them in the Mega designer, then going back into the Menu manager to reset their access levels, but they're still losing their Mega settings.

Be great to be able to assign a custom css class to Menu Item's.

Scenario 1

In the Mega Menu, you want 1 of your menu item's to stand out more and have different styling than the others, think of a 'DONATE' button. Currently the only way to do this is to probably target the menu item id written out, but it be great if I could just assign a class 'menu-donate' or 'item-highlight' that would get written on the LI tag to target it easier.

Scenario 2

On mobile devices, I might not want all of the menu items to show. So if I could assign 'hidden-phone' class to a menu item, it would just auto hide. This would be much easier than having to manually target those menu items in your stylesheets.

This feature would need to be available to all menu modules.

• When T3 is not default template, in the Navigation setting, if megamenu is enabled --> the megamenu setting loads whole site. It is expected that it should be the same as when T3 is default template.
  

1. Go to Navigation and add a sub menu to an item (not have child)
2. Go to Menu Manager and add a new menu item as a child of the menu item above.
3. Go back to Nagivation, see error as image
   

When editing the template on this link
/administrator/index.php?option=com_templates&view=style&layout=edit&id=9#overview

results in an warning.
Warning: Invalid argument supplied for foreach() in /home/XXX/public_html/XXXX/plugins/system/jat3v3/t3v3base/html/mod_menu/default.php on line 23

Joomla 3.0.2
T3 v1.0.3

We don't see this causing any issues, but this warning shows all the time at the top when editing the template. If one creates a copy, the same error is also there.

• Access the template page of T3 blank
  --> Template title is duplicated.
  

From a user on our forum:

We'll often develop sites behind a index.html temporary page - when you do that the layout preview and Theme Magic function doesn't work - it loads that index page.

I havent tested this but I assume it's correct.

• T3 framework is disabled
• Open T3 blank template setting
  --> We have a template with no settings available. We should notify user to enable T3 framework plugin.

• Please check image to see error

At the moment if you have a number of themes created for the template the size of the zip becomes very large because we end up packing a new version of the same css file in each theme folder.

I know why this was doen to simplify the process of finding the css but I think that it would be better to have this structure:

css/
css/all common css files here
css/theme/mytheme/only css related to the theme.css

I understand T3 has a set of HTML Overrides that override the Joomla Core output built into the T3 Plugin. I was wondering if we could allow for multiple HTML Overrides in the plugin that then would be selectable in the Plugin or via the Theme interface?

Scenario 1:

X Theme company wants to create their own HTML Override's specific to there needs. They might be wanting to move to the T3 Framework, and to ease the Template conversion process, move their existing overrides to T3. They wouldn't want these overrides to be in each template, but in the plugin so there is only 1 code base to update for all their templates.

Scenario 2:

X Developer just might not agree with the HTML coding approach of T3 and want to create there own. They wouldn't want to modify the T3 Core HTML Overrides because this would cause updating issues. They also would want their overrides to rest in the plugin, and not in the individual templates so there is only 1 code base/copy they need to worry about.

Scenario 3 (Soapbox Specific):

Similar to Scenario 1, we have tons of templates on J1.5 Custom HTML overrides. It would be nice to create a setup of our own overrides that mimic our J1.5 HTML as closely as possible so the conversion to T3 is easier. So sites that we are porting from our old platform, we can just easily change a parameter from using the T3 Overrides to using our J1.5 setup in the plugin. This would be great because we wouldn't have to re-write all our CSS for those sites making the switch.