News

Next step in the NFDI building process: Grant application submitted

On Tuesday the 15th October the DataPLANT NFDI consortium submitted it's proposal to the DFG. The consortium in Fundamental Plant Research consists of roughly 30 participants including universities and large research institutions distributed over the country. A significant proportion of the participants originate from Baden-Württemberg and the BioDATEN Science Data Center. Further co-applicants are the Technical University of Kaiserslautern and the Forschungszentrum Jülich.

The central aim of the DataPLANT consortium is to advance research data management in it's designated community and generate added value in the field of basic plant research. Successful collaboration and use of data of different modalities – from many sources and experiments, pre-processed or analysed with a variety of algorithms – requires contextualization of the data. The FAIR Data 1 and Linked Open Data Principles provide critical guidelines for research data management. Various consortia have therefore made proposals for best practice and compliance with these principles, but it is almost always the initiative of individual researchers to implement them. Therefore, comprehensive information on the required quality for use by third parties is rarely available. Researchers have been shown to require practical assistance in exploiting the fragmented and complex resource landscape. This increases the need for a tailor-made (infra)structure for research data management. By combining technical expertise in the fields of fundamental plant research, information and computer sciences and infrastructure specialists, DataPLANT will support plant scientists in every RDM concerns. DataPLANT will create a service environment to contextualize research data according to the FAIR principles with minimal additional effort and to support the entire research cycle in modern plant biology. The tailor-made service landscape in DataPLANT will consist of technical-digital assistance as well as on-site personnel assistance. DataPLANT thus creates a central entry point and a valuable subject-specific data and knowledge resource. In combination with teaching and training concepts, data literacy is strengthened and a long-term motivation for the creation of well-indicated data objects is generated. By integrating plant science into the NFDI network as a whole, DataPLANT is driving the digital transformation and democratization of research data in the field.

Science Data Center BioDATEN as part of the NFDI process

Together with colleagues from Tübingen, Konstanz, Freiburg, Heidelberg, ... parts of the BioDATEN community joined forces with the DaPLUS+ consortium from Kaiserlautern, Jülich and Düsseldorf to paticipate in the process to create a National Research Data Infrastructure. The newly formed consortium centers around plant data in bioinformatics and handed in a binding "Letter of Interest".

In modern hypothesis-driven science, researchers increasingly rely on effective research data management services and infrastructures that facilitate the acquisition, processing, exchange and archival of research data sets, to enable the linking of interdisciplinary expertise and the combination of different analytical results. The immense additional insight obtained through comparative and integrative analyses provides additional value in the examination of research questions that goes far beyond individual experiments. Specifically, in the research area of fundamental plant research that this consortium focuses on, modern approaches need to integrate analyses across different system levels (such as genomics, transcriptomics, proteomics, metabolomics, phenomics). This is necessary to understand system-wide molecular physiological responses as a complex dynamic adjustment of the interplay between genes, proteins and metabolites. As a consequence, a wide range of different technologies as well as experimental and computational methods are employed to pursue state-of-the-art research questions, rendering the research objective a team effort across disciplines. The overall goal of DataPLANT is to provide the research data management practices, tools, and infrastructure to enable such collaborative research in plant biology. In this context, common standards, software, and infrastructure can ensure availability, quality, and interoperability of data, metadata, and data-centric workflows and are thus a key success factor and crucial precondition in barrier-free, high-impact collaborative plant biology research. Toward this, the key objectives pursued by this consortium are:

  1. A specific community standard for fundamental plant research (meta)data and workflow annotation, based on generic, existing and emerging standards (e.g., ISA model, MIAPPE) and ontologies in plant science.
  2. Assistive mechanisms and services to build, link and maintain the complete research context during data acquisition, curation, analysis, and publication.
  3. Mechanisms for collaborative research based on enrichment and automatized crosslinking of plant-research specific (meta)data to facilitate research context management.
  4. A cloud-based open reference implementation of these mechanisms and services, and a central hosted instance thereof.
  5. A robust, federated infrastructure both for data computation and management covering the complete data lifecycle.
  6. Comprehensive training of community members through workshops and summer schools and providing open training material.

The final grant application is due to the 15th October.

Science Data Center "BioDATEN" at GCC 2019 conference in Freiburg

(Source: RUF)

The just started Science Data Center "BioDATEN" was present at this year's Galaxy conference in Freiburg, the GCC 2019. The Science Data Center BioDATEN - Bioinformatics DATa ENvironment is a community effort in standardization, services and sustainable research data management. It plans to combine the tools and services provided in frameworks like Galaxy with efforts towards standardization and research data management.

The digitalization changes the working habits in almost all scientific disciplines with vast impact on teaching, research and interdisciplinary collaboration. The challenges faced in bioinformatics arising from vastly growing amounts of data are exemplary for a discipline establishing new ways of scientific work and insight. Galaxy as a platform already provides a wide range of tools used by a significant proportion of the community presented in BioDATEN. Through the formed consortium, comprising of bioinformaticians, core facilities, compute centers and libraries, a science data center for life sciences for Baden-Württemberg just got established. The four-year project will report about the anticipated goals and the work plan intended to achieve them in the relevant communities.

BioDATEN will heavily depend on the technical infrastructure available through Galaxy and the project partners such as bwSFS, BinAC and bwCloud or the repositories provided by the university libraries in Konstanz and Tübingen. State-wide activities will be orchestrated through the work group on research data management. The SDC creates a multi institutional network among the strongest bioinformatics research sites. The consortium brings together the compute centers of the universities of Freiburg and Tübingen; the DKFZ, the EMBL and the university (BioQuant) in Heidelberg; the university libraries of Konstanz and Tübingen; the Quantitative Biology Center Tübingen; Bioinformatics and Plant Biotechnology Freiburg; CLARIN-D Center Tübingen; Livestock Microbial Ecology Hohenheim; Disease Ecology and Evolutionary Genetics Konstanz; Clinic of Neurology Ulm.

The project within the third line of the eScience initiative of the state - the BioDATEN SCD is funded by the Ministry of Science, Research and the Arts Baden-Württemberg - got acquired and is handled by the eScience group of the computer center. It is part of the RDMG activities. The conference poster at GCC 2019 is one of it's first activities.

Sponsored by:

  • Ministerium für Wissenschaft, Forschung und Kunst Baden-Württemberg
  • Ministerium für Wissenschaft, Forschung und Kunst Baden‑Württemberg

Debug Console

Close15 MBRequestSessionTimelineDatabase24Events25
$_GET
Array( limit => 3, start => 15 ) Array(
limit => 3,
start => 15
)
$_POST
Array( ) Array(

)
$_COOKIE
Array( ) Array(

)
$_SERVER
Array( USER => apache, HOME => /usr/share/httpd, FCGI_ROLE => RESPONDER, REDIRECT_UNIQUE_... Array(
USER => apache,
HOME => /usr/share/httpd,
FCGI_ROLE => RESPONDER,
REDIRECT_UNIQUE_ID => X8Z5n7H@G6doWzBQlHc11QAAAAI,
REDIRECT_SCRIPT_URL => /news,
REDIRECT_SCRIPT_URI => https://portal.biodaten.info/news,
REDIRECT_HTTPS => on,
REDIRECT_STATUS => 200,
UNIQUE_ID => X8Z5n7H@G6doWzBQlHc11QAAAAI,
SCRIPT_URL => /news,
SCRIPT_URI => https://portal.biodaten.info/news,
HTTPS => on,
HTTP_USER_AGENT => CCBot/2.0 (https://commoncrawl.org/faq/),
HTTP_ACCEPT => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8,
HTTP_ACCEPT_LANGUAGE => en-US,en;q=0.5,
HTTP_ACCEPT_ENCODING => br,gzip,
HTTP_HOST => portal.biodaten.info,
HTTP_X_FORWARDED_PROTO => https,
HTTP_X_FORWARDED_FOR => 18.213.192.104,
HTTP_CONNECTION => close,
PATH => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin,
SERVER_SIGNATURE => ,
SERVER_SOFTWARE => Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips,
SERVER_NAME => portal.biodaten.info,
SERVER_ADDR => 192.168.15.64,
SERVER_PORT => 443,
REMOTE_ADDR => 192.168.15.107,
DOCUMENT_ROOT => /var/www/biodatenhub4,
REQUEST_SCHEME => https,
CONTEXT_PREFIX => ,
CONTEXT_DOCUMENT_ROOT => /var/www/biodatenhub4,
SERVER_ADMIN => root@localhost,
SCRIPT_FILENAME => /var/www/biodatenhub4/index.php,
REMOTE_PORT => 35544,
REDIRECT_QUERY_STRING => limit=3&start=15,
REDIRECT_URL => /news,
GATEWAY_INTERFACE => CGI/1.1,
SERVER_PROTOCOL => HTTP/1.1,
REQUEST_METHOD => GET,
QUERY_STRING => limit=3&start=15,
REQUEST_URI => /news?limit=3&start=15,
SCRIPT_NAME => /index.php,
PHP_SELF => /index.php,
REQUEST_TIME_FLOAT => 1606842783.6673,
REQUEST_TIME => 1606842783
)
session.client.forwarded 18.213.192.104
separator .
orderBy id
orderDir asc
1 registerIP
2 access
always
renew
tracker.sid b826d92a2679a32cb2ade39e7ae42256
tracker.ssid b826d92a2679a32cb2ade39e7ae42256
tracker.rsid b826d92a2679a32cb2ade39e7ae42256
  • site 0.065 seconds (+0.065); 9.25 MB (+9.250) - afterInitialise
  • site 0.085 seconds (+0.020); 10.50 MB (+1.250) - afterRoute
  • site 0.162 seconds (+0.077); 14.25 MB (+3.750) - afterDispatch
  • site 0.177 seconds (+0.015); 14.50 MB (+0.250) - beforeRenderModule mod_custom (Footer)
  • site 0.179 seconds (+0.002); 14.50 MB (0.000) - afterRenderModule mod_custom (Footer)
  • site 0.179 seconds (+0.001); 14.75 MB (+0.250) - beforeRenderModule mod_collect (Collect)
  • site 0.181 seconds (+0.001); 14.75 MB (0.000) - afterRenderModule mod_collect (Collect)
  • site 0.181 seconds (+0.000); 14.75 MB (0.000) - beforeRenderModule mod_menu (Main Menu)
  • site 0.184 seconds (+0.004); 14.75 MB (0.000) - afterRenderModule mod_menu (Main Menu)
  • site 0.187 seconds (+0.003); 14.75 MB (0.000) - onAfterRender
  • site 0.190 seconds (+0.003); 14.75 MB (0.000) - sessionStore
15 MB

24 Queries Logged: 0.019397974014282 seconds

  1. SELECT data
      FROM `jos_session`
      WHERE `session_id` = 'e617552eb41c2085b13a00d13770f5ce'
  2. DELETE
      FROM `jos_session`
      WHERE `session_id` = 'e617552eb41c2085b13a00d13770f5ce'
  3. SELECT data
      FROM `jos_session`
      WHERE `session_id` = 'b826d92a2679a32cb2ade39e7ae42256'
  4. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_languages'
  5. SELECT session_id
      FROM `jos_session`
      WHERE `session_id` = 'b826d92a2679a32cb2ade39e7ae42256'
      LIMIT 1
  6. INSERT INTO `jos_session` (`session_id`,`client_id`,`time`,`ip`)
      VALUES ('b826d92a2679a32cb2ade39e7ae42256','0','1606842783','192.168.15.107')
  7. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_members'
  8. SELECT b.id
      FROM `jos_usergroups` AS `a`
      LEFT JOIN jos_usergroups AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`id` = '1'
  9. SELECT *
      FROM `jos_viewlevels`
  10. SELECT folder AS type,element AS name,protected,params
      FROM `jos_extensions`
      WHERE `enabled` >= '1'
      AND `type` = 'plugin'
      AND `state` >= '0'
      AND `access` IN ('1','1','4')
      ORDER BY `ordering` ASC
  11. SELECT m.id,m.menutype,m.title,m.alias,m.note,m.path AS route,m.link,m.type,m.level,m.language,m.browserNav,m.access,m.params,m.home,m.img,m.template_style_id,m.component_id,m.parent_id,e.element AS component
      FROM `jos_menu` AS `m`
      LEFT JOIN jos_extensions AS e
      ON e.extension_id = m.component_id
      WHERE `m`.`published` = '1'
      AND `m`.`parent_id` > '0'
      AND `m`.`client_id` = '0'
      ORDER BY `m`.`lft` ASC
  12. SELECT jos_template_styles.id,jos_template_styles.home,jos_template_styles.template,jos_template_styles.params,jos_extensions.protected
      FROM `jos_template_styles`
      INNER JOIN jos_extensions
      ON jos_extensions.element = jos_template_styles.template
      WHERE `jos_template_styles`.`client_id` = '0'
      AND `jos_extensions`.`enabled` = '1'
      AND `jos_extensions`.`type` = 'template'
      AND jos_extensions.`client_id` = `jos_template_styles`.`client_id`
      ORDER BY `home` DESC
  13. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_content'
  14. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_categories'
  15. SELECT a.rules
      FROM `jos_assets` AS `a`
      WHERE `a`.`id` = '1'
      GROUP BY a.id, a.rules, a.lft
  16. SELECT b.rules
      FROM `jos_assets` AS `a`
      LEFT JOIN jos_assets AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`name` = 'com_content'
      GROUP BY b.id, b.rules, b.lft
      ORDER BY `b`.`lft` ASC
  17. SELECT c.*,
      CASE WHEN CHAR_LENGTH(c.alias) THEN CONCAT_WS(':', c.id, c.alias) ELSE c.id END as slug,COUNT(i.`id`) AS numitems
      FROM `jos_categories` AS `c`
      LEFT JOIN jos_categories AS s
      ON (s.lft <= c.lft
      AND s.rgt >= c.rgt) OR (s.lft > c.lft
      AND s.rgt < c.rgt)
      LEFT JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      LEFT JOIN `jos_content` AS i
      ON i.`catid` = c.id
      AND i.state = 1
      WHERE (`c`.`extension` = 'com_content' OR `c`.`extension` = 'system' )
      AND `c`.`access` IN ('1','1','4')
      AND `c`.`published` = '1'
      AND `s`.`id` = '26'
      AND badcats.id is null
      GROUP BY c.id,c.asset_id,c.access,c.alias,c.checked_out,c.checked_out_time,c.created_time,c.created_user_id,c.description,c.extension,c.hits,c.language,c.level,c.lft,c.metadata,c.metadesc,c.metakey,c.modified_time,c.note,c.params,c.parent_id,c.path,c.published,c.rgt,c.title,c.modified_user_id
      ORDER BY `c`.`lft` ASC
  18. SELECT b.rules
      FROM `jos_assets` AS `a`
      LEFT JOIN jos_assets AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`name` = 'com_content.category.26'
      GROUP BY b.id, b.rules, b.lft
      ORDER BY `b`.`lft` ASC
  19. SELECT a.*,a.id,a.title,a.alias,a.title_alias,a.introtext,a.language,a.checked_out,a.checked_out_time,a.catid,a.created,a.created_by,a.created_by_alias,
      CASE WHEN a.modified IS NULL THEN a.created ELSE a.modified END AS modified,a.modified_by,uam.name AS modified_by_name,
      CASE WHEN a.publish_up IS NULL THEN a.created ELSE a.publish_up END AS publish_up,a.publish_down,a.images,a.urls,a.attribs,a.metadata,a.metakey,a.metadesc,a.access,a.hits,a.featured,a.xreference,a.fulltext AS readmore,
      CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title,c.path AS category_route,c.access AS category_access,c.alias AS category_alias,
      CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating,v.rating_count AS rating_count,c.published,
      CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published
      FROM `jos_content` AS `a`
      LEFT JOIN jos_content_frontpage AS fp
      ON fp.content_id = a.id
      LEFT JOIN jos_categories AS c
      ON c.id = a.catid
      LEFT JOIN jos_users AS ua
      ON ua.id = a.created_by
      LEFT JOIN jos_users AS uam
      ON uam.id = a.modified_by
      LEFT JOIN jos_categories as parent
      ON parent.id = c.parent_id
      LEFT JOIN jos_content_rating AS v
      ON a.id = v.content_id
      LEFT
      OUTER JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      WHERE `a`.`access` IN ('1','1','4')
      AND `c`.`access` IN ('1','1','4')
      AND
      CASE WHEN badcats.id is null THEN a.state ELSE 0 END IN (1)
      AND `a`.`catid` = '26'
      AND (`a`.`publish_up` IS NULL OR `a`.`publish_up` <= '2020-12-01 17:13:03' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2020-12-01 17:13:03' )
      ORDER BY `a`.`publish_up` DESC,`a`.`created` DESC
      LIMIT 9223372036854775807
  20. SELECT a.*,a.id,a.title,a.alias,a.title_alias,a.introtext,a.language,a.checked_out,a.checked_out_time,a.catid,a.created,a.created_by,a.created_by_alias,
      CASE WHEN a.modified IS NULL THEN a.created ELSE a.modified END AS modified,a.modified_by,uam.name AS modified_by_name,
      CASE WHEN a.publish_up IS NULL THEN a.created ELSE a.publish_up END AS publish_up,a.publish_down,a.images,a.urls,a.attribs,a.metadata,a.metakey,a.metadesc,a.access,a.hits,a.featured,a.xreference,a.fulltext AS readmore,
      CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title,c.path AS category_route,c.access AS category_access,c.alias AS category_alias,
      CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating,v.rating_count AS rating_count,c.published,
      CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published
      FROM `jos_content` AS `a`
      LEFT JOIN jos_content_frontpage AS fp
      ON fp.content_id = a.id
      LEFT JOIN jos_categories AS c
      ON c.id = a.catid
      LEFT JOIN jos_users AS ua
      ON ua.id = a.created_by
      LEFT JOIN jos_users AS uam
      ON uam.id = a.modified_by
      LEFT JOIN jos_categories as parent
      ON parent.id = c.parent_id
      LEFT JOIN jos_content_rating AS v
      ON a.id = v.content_id
      LEFT
      OUTER JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      WHERE `a`.`access` IN ('1','1','4')
      AND `c`.`access` IN ('1','1','4')
      AND
      CASE WHEN badcats.id is null THEN a.state ELSE 0 END IN (1)
      AND `a`.`catid` = '26'
      AND (`a`.`publish_up` IS NULL OR `a`.`publish_up` <= '2020-12-01 17:13:03' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2020-12-01 17:13:03' )
      ORDER BY `a`.`publish_up` DESC,`a`.`created` DESC
      LIMIT 15,3
  21. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_search'
  22. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_users'
  23. SELECT m.id,m.title,m.module,m.position,m.content,m.showtitle,m.params,mm.menuid,e.protected
      FROM `jos_modules` AS `m`
      LEFT JOIN jos_modules_menu AS mm
      ON mm.moduleid = m.id
      LEFT JOIN jos_extensions AS e
      ON e.element = m.module
      AND e.client_id = m.client_id
      WHERE `m`.`published` = '1'
      AND `e`.`enabled` = '1'
      AND (`m`.`publish_up` IS NULL OR `m`.`publish_up` <= '2020-12-01 17:13:03' )
      AND (`m`.`publish_down` IS NULL OR `m`.`publish_down` >= '2020-12-01 17:13:03' )
      AND `m`.`access` IN ('1','1','4')
      AND `m`.`client_id` = '0'
      AND (`mm`.`menuid` = '153' OR `mm`.`menuid` <= '0' )
      ORDER BY `m`.`position` ASC,`m`.`ordering` ASC
  24. UPDATE `jos_session`
      SET `data` = '__default|a:10:{s:15:\"session.counter\";i:1;s:19:\"session.timer.start\";i:1606842783;s:18:\"session.timer.last\";i:1606842783;s:17:\"session.timer.now\";i:1606842783;s:24:\"session.client.forwarded\";s:14:\"18.213.192.104\";s:8:\"registry\";O:23:\"Hubzero\\Config\\Registry\":2:{s:7:\"\0*\0data\";O:8:\"stdClass\":1:{s:1:\"0\";s:7:\"session\";}s:9:\"separator\";s:1:\".\";}s:4:\"user\";C:17:\"Hubzero\\User\\User\":22:{a:1:{s:5:\"guest\";b:1;}}s:11:\"tracker.sid\";s:32:\"b826d92a2679a32cb2ade39e7ae42256\";s:12:\"tracker.ssid\";s:32:\"b826d92a2679a32cb2ade39e7ae42256\";s:12:\"tracker.rsid\";s:32:\"b826d92a2679a32cb2ade39e7ae42256\";}',`time` = '1606842783',`ip` = '192.168.15.107'
      WHERE `session_id` = 'b826d92a2679a32cb2ade39e7ae42256'
  • onAfterInitialise Method plgSystemP3p::onAfterInitialise /core/plugins/system/p3p/p3p.php:21
  • onAfterInitialise Method plgSystemRemember::onAfterInitialise /core/plugins/system/remember/remember.php:20
  • onAfterInitialise Method plgSystemHubzero::onAfterInitialise /core/plugins/system/hubzero/hubzero.php:21
  • onAfterInitialise Method plgSystemXFeed::onAfterInitialise /core/plugins/system/xfeed/xfeed.php:21
  • onAfterInitialise Method plgSystemSupergroup::onAfterInitialise /core/plugins/system/supergroup/supergroup.php:113
  • onAfterInitialise Method plgSystemReferrerpolicy::onAfterInitialise /core/plugins/system/referrerpolicy/referrerpolicy.php:21
  • onAfterRoute Method plgSystemJquery::onAfterRoute /core/plugins/system/jquery/jquery.php:21
  • onAfterRoute Method plgSystemSpamjail::onAfterRoute /core/plugins/system/spamjail/spamjail.php:21
  • onAfterRoute Method plgSystemIncomplete::onAfterRoute /core/plugins/system/incomplete/incomplete.php:21
  • onAfterRoute Method plgSystemUnconfirmed::onAfterRoute /core/plugins/system/unconfirmed/unconfirmed.php:21
  • onAfterRoute Method plgSystemUnapproved::onAfterRoute /core/plugins/system/unapproved/unapproved.php:21
  • onAfterRoute Method plgSystemPassword::onAfterRoute /core/plugins/system/password/password.php:21
  • onContentPrepare Method plgContentLoadmodule::onContentPrepare /core/plugins/content/loadmodule/loadmodule.php:35
  • onContentPrepare Method plgContentEmailcloak::onContentPrepare /core/plugins/content/emailcloak/emailcloak.php:25
  • onContentPrepare Method plgContentPagebreak::onContentPrepare /core/plugins/content/pagebreak/pagebreak.php:35
  • onContentPrepare Method plgContentXhubtags::onContentPrepare /core/plugins/content/xhubtags/xhubtags.php:25
  • onContentPrepare Method plgContentFormatwiki::onContentPrepare /core/plugins/content/formatwiki/formatwiki.php:63
  • onContentPrepare Method plgContentFormathtml::onContentPrepare /core/plugins/content/formathtml/formathtml.php:105
  • onContentPrepare Method plgContentExternalhref::onContentPrepare /core/plugins/content/externalhref/externalhref.php:41
  • onContentBeforeDisplay Method plgContentPagenavigation::onContentBeforeDisplay /core/plugins/content/pagenavigation/pagenavigation.php:25
  • onContentBeforeDisplay Method plgContentVote::onContentBeforeDisplay /core/plugins/content/vote/vote.php:32
  • onAfterDispatch Method plgSystemMobile::onAfterDispatch /core/plugins/system/mobile/mobile.php:22
  • onAfterDispatch Method plgSystemDebug::onAfterDispatch /core/plugins/system/debug/debug.php:60
  • onAfterDispatch Method PlgSystemHighlight::onAfterDispatch /core/plugins/system/highlight/highlight.php:25
  • onAfterRender Method plgSystemSef::onAfterRender /core/plugins/system/sef/sef.php:21