Please, Could you check if mentions and hashtag are working in alpha2? I have no success with them.
It seems our old calendar.js does not work for alpha2
There is a modern replacement in htdocs libraries jscore app modules i18n main.js but it seems deactivated.
Too modify include/calendarjs.php. More files involved?
Quote:
skenow wrote:
The problem with the module icons not displaying is in the block template (or the block function, if you want the smarty var to be $mod.image instead of $mod.iconbig)
Creating a Branch in Git (and why) http://www.youtube.com/watch?v=CQnh2pDM26k
No, I don't have the knowledge to do it. Right now I learn step by step the GIT.
I have installed on a Windows environment and the paths were saved correctly. I am even using PHP 5.4 in that environment. (worked in the PHP 5.3 environment on Windows, too).
They still work, if you manually add them to your text. The buttons were only added to the DHTML editor. They should really move outside the editor, anyway.
@sato-san - did you create a branch for those changes, so they can be viewed separately and then merged to the main 2.0 branch?
Quote:
sato-san on 2013/5/6 11:20:36
I added today two "clear:both" in the style, and afterthem was fine. Do you have a chance to testing the latest branch from GIT?
The problem with the module icons not displaying is in the block template (or the block function, if you want the smarty var to be $mod.image instead of $mod.iconbig)
imLinks is using javascript for some extra features only. These features can be activated and deactivated from the Preferences and are not causing any issues.
Because DHTML editor is out (althought it is a hidden folder), what about plugins ( Mentions, hastags, source code, wiki, etc.)
They do not work in TinyMCE and the code buttons is for DHTML
@McDonald - we will need to spend some time updating imLinks to use modern javascript before I can be comfortable with using it as a benchmark.
As much as I would like to maintain backwards compatibility - imLinks is leveraging 10 year old javascript, which is bound to create issues. If you would like my assistance updating imLinks to take advantage of the new architecture in 2.0 - I would be happy to help.
I added today two "clear:both" in the style, and afterthem was fine. Do you have a chance to testing the latest branch from GIT?
Yes. However in Content module admin header menus are availables.
About problems with FF I confirmed them: modules/system/admin.php?fct=blocks looks bad. It is strange because other modern browser have not that problem (tested in Opera and Chrome)
Hi Will
about : # 1 and #6: forget them.. It seems there were uploading files to the server
#8
Quote:
For #8 - is there an adminMenu_spanish file in your cache directory? When you switch languages this file needs to be generated and should re-appear once you reach a page that triggers its creating. Correct?
Hello,
I installed the latest branch from 2.0 after I committed some bugfixes.
Now I noticed, that the header menus from IPF modules in the module ACP are not longer available.
Example: cms module - I have some $headermenu defined, but displayed are other menus.
Does can anyone reproduce it?
@fiammybe, it looks fine in Opera too. Looks like a FF issue.
With Opera I have the idea the automatic redirection doesn't work...
Something else I noticed is the absence of the 'All' button in the debugger line.
The wonders of browser compatibility I'll create a ticket for it anyway, so we can see if it can be sorted out on all platforms.
Thinks are getting weird now.
I've done the testings and findings mentioned above with FireFox 20.0.1.
As mentioned the listing of the links in Main Index in the imLinks module doesn't look good. See also the above screenshot.
Now, I just switched back to my main browser, Internet Explorer 10, and guess what....... The listing of the ipf table looks fine in IE10.